Drafts and going live

Every change is a draft first. So you cannot break the live site by asking for a change, and neither can anyone else with a key.

Two layers

Your site has two layers: live, what visitors see, and draft, staged next to it. Every change — a new page, a corrected price, a replaced image, an edited template — lands in the draft layer. The live site does not know it exists.

The draft layer is shared: two people’s drafts sit side by side, and either can see the whole picture. A colleague with the right to publish may publish work someone else staged.

Seeing it before anyone else does

Ask your agent what is staged and you get the list, with a preview link. Your agent can also search the round: search with layer: "both" finds a staged page next to the live ones (a staged version wins over its live one, its snippet shows the staged words, and every hit says which layers it has), so a new page can be linked, listed or checked before it goes live; /edit’s ⌘K and list chooser search that way. The preview shows the entire site as it would be with everything staged published: the new page in the real menu, in its place in the overviews and on /graph, with the real images, in every language. A staged data file that is empty or broken is gone in the preview — its page, its rows, its search hits — and the audit refuses to publish it. One exception: a replacement for an image or file that is already live still shows the live one in the preview — your agent can hand you a link to the staged file itself. The link is a secret; whoever holds it sees the draft. Renew it and the old link stops working; when the last draft is published or dropped the round closes and the link dies with it. While you look at a preview, a small bar sits at the bottom of every page: it says Draft preview, offers Copy preview link (the same secret link, ready to paste to whoever should have a look) and Exit preview.

For a small change, your agent can also show the difference between draft and live.

Publishing

Publishing moves a draft to live: one thing, a chosen set, or everything staged. A set goes live as a whole or not at all, so a new page and the menu item pointing to it never arrive separately.

Before anything goes live, the site checks itself as it would be with the draft in it: every link resolves — in templates and in the text of your pages alike, images and files included — every required field is filled, every template parses and the site’s own settings still boot. A dead link in something you are publishing refuses the publish; one already live is reported, not blocking. (A link is what sits in an href or src inside page text; a plain address in a data field is not checked as one.) If something is wrong, publishing is refused and you are told what. A draft that leans on another draft not being published is refused too. The check is the same for everyone and cannot be skipped.

Publishing needs the right to publish. A key that may write but not publish can stage as much as it likes; the work waits for someone who may.

Dropping, and taking back

Action What happens
Drop a draft It disappears from the draft layer; the live site was never affected.
Take back something live It returns to draft, where you fix and republish, or drop it.
Remove for good Take back, then drop. Reversible until the last step; even then the file is in history.

Taking back is refused if it would break what remains — a page, image or file that a template or another page’s text still links to, or the home page — so fix the references first. A few files never leave live at all, because the site cannot answer without them: the site’s settings, its helpers, its route table, the universal page template and the organisation entity. Change those with an update and a publish instead. See History and undo.