Publishing
Nothing goes live by accident.
Every word you and the AI write is a draft. One button sends the lot, after refusing anything structurally broken — and every version that was ever live is still there to go back to.
No Save button
Autosaved to a draft as you type. Closing the tab costs you a second, not an afternoon.
One Publish
It shows you what is waiting, refuses what is broken, and sends everything at once.
Always a way back
A version is kept every time you publish, with who published it and what changed.
Two copies of everything
What you are editing and what the world sees are different things.
Every page and every setting exists twice: the draft you and the AI are working on, and the published version your visitors see. That one idea is where most of this page comes from.
The draft
Where all the work happens.
- Autosaved as you type, and as the AI writes.
- What the preview builds from, so the preview is honest.
- Two tabs or two people can work on it at once.
- Renaming a page changes its address here and nowhere else yet.
The published copy
Immutable, and the only thing served.
- Written when you publish, and never touched again afterwards.
- Every visitor sees this and nothing else.
- Half-finished work cannot reach it, because nothing writes to it directly.
- The old address keeps working until the rename is published.
Pressing the button
It checks the site before it changes anything.
Putting an AI-built site live is a bigger deal than saving a document — the AI wrote the pages, and there is no separate switch afterwards to catch a mistake. So the checks run first, and a refused publish leaves your live site exactly as it was.
Code that will not run
If your site has custom code and a character is out of place, every page breaks at once — and nothing on screen would tell you, because the preview is broken in exactly the same way. It is checked before anything goes out.
Two pages at one address
Two pages cannot both live at /services. Caught before anything moves, and reported as a sentence naming the address and which page already has it.
A forward that goes in circles
A rule sending visitors to an address that sends them back is a page that never finishes loading. Easy to create by moving pages around, and impossible to spot by reading the list.
A colour that does not exist
A page asking for a colour or typeface your site has not got. A warning rather than a refusal, because you may be about to add it — but worth saying, because this is the failure that quietly puts an entire site in the wrong font while nothing anywhere reports a problem.
Only what you changed is checked, so a page nobody has touched never holds up a release. And the distinction is deliberate: refusing over matters of taste rather than over things that are actually broken would make Publish something people learn to work around.
Afterwards
A record of what happened, and a way to undo it.
Versions that were really live
A version is kept when you publish, not every time you type — so the history is a short list of what visitors actually saw, each with who published it and what changed since the one before. Restoring one is a click.
An activity feed for the site
Every publish, every AI conversation, every page created or deleted, every file, every domain change and every charge, in one place, with a link to where the thing is now. It is what you read when the question is “when did that change, and who changed it”.
A bill you can check
Every AI turn and every generated image is a row: the prompt, who sent it, which model, the outcome, and what it cost in credits — linked to the conversation that caused it. An itemised bill that does not add up is worse than no bill.
Questions about publishing
Where is the Save button?
There is not one. Everything you type is saved to a draft about a second and a half after you stop typing, on blur, and when you leave the screen. Closing the tab in the middle of writing costs you at most a second of work, where a Save button costs you everything you had not pressed it for.
Can I publish just one page?
No, deliberately. Sending one page on its own can leave the live site actually broken rather than merely out of date — a section you moved to a different page, a colour the new design needs. Publish sends everything you have changed, and shows you exactly what that is before you press it.
What can stop a publish?
Code on your site that will not run, two pages claiming the same web address, and a forwarding rule that sends visitors round in a circle. Those are broken rather than a matter of taste — and each is the kind of thing that would take the site down without anything on screen telling you.
And what only warns?
A page referring to a colour your site does not have, a site with no pages, a site with no home page. Each of those might be deliberate, or a minute away from being fixed. Refusing to publish over things that might be on purpose turns Publish into something people learn to fight, and the next step from there is a switch to turn it off.
How far back can I go?
To any version that was actually live. A version is kept when you publish, not every time you type, so the history is a short readable list of what visitors saw rather than several hundred saves. Each one records who published it and what changed since the one before.
Can I see what the site will look like before publishing?
Yes — the preview is built from your drafts, so it is genuinely what you are about to release rather than an approximation of it. The live version is one click away in the same bar, and the screen says plainly when the two are different.