Skip to main content
Your published site is a snapshot. It stays exactly as it was until you publish again — even as you keep building.

Before you start

A workspace you have already published once, and at least one change you want to ship.

Publish an update

1

Make your change

Ask the Builder for it in the conversation and wait for the preview to show it.Expected result: the change is visible in the preview pane and the Builder has reported the milestone done.
2

Publish again

Select Publish. There is no naming dialog this time — your address is already claimed — but the Review before publishing dialog still shows you the version going out. Select Approve and publish.Expected result: the button reads Deploying….
3

Wait, then check

Deployment takes a few minutes. When it finishes, open your Live at … link.Expected result: your public site now shows the change.
Hard-refresh the tab, or open the site in a private window, if your browser is showing you a cached copy.

Why it works this way

Two useful consequences:
  • You can build in the open without breaking what people see. Experiment freely; the live site is unaffected until you decide.
  • Publishing is a decision. Nothing reaches your audience by accident.
Publishing always ships your last completed milestone. If the Builder is mid-change when you publish, the last finished state goes out — not the half-finished one.

If a publish fails

A failed publish leaves your existing live site untouched. Visitors keep seeing the last good version. Your claimed address is also safe — a failed publish never releases the name. Select Publish to try again. If it keeps failing, ask the Builder what went wrong; it reports failures honestly rather than claiming success.

Verify

  • Your Live at … link shows the change in a private window.
  • The change is the one you asked for and nothing else obviously moved.

Troubleshooting

Next

Work with the Builder

Make the next change.

How credits work

What publishing costs.