Code + Visual Editor

A Tanqory theme has two layers, and you work on them in two places — section code is kept separate from theme settings.

Layer	Where	Who
Code — section components (.tsx) + their defineSection schema	Local (CLI + your editor)	Developer
Content — which sections are on each page and their setting values	Visual editor (browser)	You / the merchant

Both operate on the same theme in the store. Your code defines what sections exist and what's configurable; the visual editor arranges them and sets values.

The two previews

• localhost:4321 (tanqory theme dev) — your fast local loop with hot reload and your store's live data. This is where you write section code.
• The visual editor (Customize) — opens the theme in the store and edits its content (drag sections, change settings), saved as you go.

By default these are separate: the editor shows the theme in the store, not your localhost. To make the editor reflect your local code, push it up.

Standard loop

tanqory theme dev        # write sections locally (localhost:4321)
tanqory theme push       # upload code → the editor now sees your sections
# open Customize in the store admin → arrange + configure
tanqory theme pull       # bring the editor's content/settings back to your code

Live-sync (--sync)

For a tighter, fully automatic loop, run dev with --sync. It watches your files and pushes changes to the store theme automatically, so the editor and preview reflect your edits without a manual push:

tanqory theme dev --sync

✓ Live data from my-store → http://localhost:4321
✓ Live-sync ON → store theme my-store-aurora-a1b2 (edits push automatically)
  Editor:  https://app.tanqory.com/admin/store/<id>/themes/<id>/builder

• Saves are debounced and batched into a single store-side rebuild.
• Because themes are React (compiled), the store-side preview takes a few seconds to rebuild after a change — the localhost:4321 preview stays instant.

Don't edit the same theme in both places at once

push / --sync overwrites the theme's files. If you're editing content in the visual editor and live-syncing code at the same time, one can overwrite the other. Use the editor for content, the CLI for code — and pull before you resume coding if you changed content in the editor.

Publishing

Publishing a theme to the live storefront is done from the store admin (the theme's Publish action in the Theme library), or by the merchant. The CLI is for building and pushing; tanqory theme submit is for the marketplace review flow, which is separate from publishing to a single store.