Skip to main content
The builder saves your work as you edit. Saved changes stay a draft until you publish.

​
Publish

1

Open Publish

Click Publish in the top bar. The dialog checks the whole theme first.
2

Read the check

  • No problems found: you can publish.
  • Warnings (yellow): you can still publish. The storefront ignores what they point at.
  • Errors (red): fix them before publishing. Each one names the file and, where possible, the line.
3

Publish

The theme is built and goes live on your subdomain and custom domain. The dialog shows when you last published.

​
Remove unused values

Templates can keep values that no longer match a setting, for example after you remove a setting from a schema. These show as warnings such as "old_key" is not a setting (ignored). When there are any, Publish shows Remove unused values, which deletes them from your templates in one step. You can undo it.

​
Common checks

​
Theme updates

When the theme you started from gets a new version, Update theme appears in the builder’s top bar. Updating never overwrites your edits without asking. For each file, Join Markt compares three versions: the file as installed, your current file, and the new theme file.
1

Open Update theme

The dialog lists files updated automatically, files that need your choice, and your edits that are kept.
2

Decide each conflict

Click Show changes to see your file and the update side by side. Then pick Keep mine or Use update. A file you and the update both changed keeps your version unless you pick otherwise.
3

Apply, then publish

Applying changes your saved theme. Publish to put it live.
If you chose Keep mine, Code keeps reminding you that a newer version exists for that file. Open Compare with theme to look again, and Restore theme version to take it later.

​
Platform updates

The shared storefront code under src/platform/ (cart, checkout, routing, data loading) belongs to Join Markt. When it is updated, every published store is rebuilt automatically:
  • Only your published files are used. Drafts never go live this way.
  • If you publish while the rebuild runs, your publish wins.
  • If a rebuild fails, your current live store stays as it is and the rebuild is retried later.
Open previews also pick up platform changes on their next build. You do not need to republish to get platform fixes.