For developers
Build and publish themes
A theme is a package: a manifest, tokens, templates and optional styles and script. It is validated before it can be submitted, reviewed by a person, and versioned so an update cannot break the shops already running it.
What you are building against
Not a CSS override on somebody else's markup. A theme declares what it supports, ships its own templates, and runs inside limits the platform enforces rather than requests.
A declared manifest
Name, version, the venue types it suits, the colour modes it supports and the platform range it targets โ all validated against a schema, not a convention.
A validator you run first
Template helpers, data variables and size limits are checked before submission. The reference page is generated from the same constants the validator uses, so it cannot promise something the checker rejects.
Scripts, safely
Merchant and theme JavaScript runs in a cross-origin sandbox without same-origin access, so a theme cannot reach the session of the person browsing it.
A marketplace
Free, one-off or subscription. Installs, ratings and settlement per currency, visible from your own dashboard.
From your editor to a live shop
Five steps, and you can see where a submission is at every one of them.
- 1
Build
Scaffold a theme, edit it in the studio or your own editor, and preview it against real menu data.
- 2
Validate
Run the checks yourself. Contrast, helpers, size limits and the manifest schema.
- 3
Submit
Package a version and send it. Every submission keeps its history.
- 4
Review
A person reads it against a published checklist and either approves it or tells you exactly what to change.
- 5
Publish
Approved versions go to the marketplace. Merchants choose when to take the update.
The reference is generated from the validator
The allowed helpers, the banned ones, the data variables and every size limit are imported from the engine rather than described, so the documentation and the checker cannot drift apart.