Draft and publish

Your widget has two versions at all times.

The draft is what the builder loads and what Save writes. Only your team sees it.

The published version is what visitors get. It changes only when you press Publish.

So you can leave a half-finished redesign saved for a week without a single visitor seeing it, and publish the moment it's ready.

The workflow#

1. Edit in the builder.
2. Save — as often as you like. Nothing reaches visitors.
3. Publish — the draft is copied over the published version, live immediately.

There's no scheduling and no approval step. Publish is the moment of truth.

Rolling back#

There's no version history yet, so publishing over something good means the old layout is gone. Two habits that cost nothing:

• Publish deliberately, not as a reflex after every save.
• Before a big redesign, screenshot the widget. It's a crude backup, but it has saved more layouts than it has any right to.

If you want real version history, tell us — it's a known gap, not a design decision.

A caveat worth knowing#

Publishing replaces the whole layout, not the parts you changed. If two people have the builder open, the second to publish wins and the first person's work is overwritten with no warning.

On a small team the fix is a message in Slack. On a larger one, decide who owns the widget.