Publishing
You decide when changes go live.
One button checks and publishes all pending changes. Each published version remains available to review or restore.
Automatic saving
One Publish
Published versions are kept
Before publishing
Visitors see changes only after you press Publish.
You can edit and preview the site without changing what visitors see. Publish checks the changes and puts them online together.
Your changes
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 receives this version.
- Publish replaces it only after the checks pass.
- The old address keeps working until the rename is published.
Pressing the button
It checks the site before it changes anything.
Publish checks your changes before anything goes live. A failed check leaves the current site exactly as it is.
Code that will not run
MightyBuilder parses custom code before publishing and stops the release when it cannot run.
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 that asks for an unknown colour or typeface receives a warning before publishing so you can confirm or correct it.
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
Published versions can be reviewed and restored.
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?
MightyBuilder saves your work about a second and a half after you stop typing, when a field loses focus and when you leave the screen. Closing the tab in the middle of writing can lose at most the last second of work.
What gets published?
All pending pages, shared sections and design changes go live together. The Publish panel shows the full list before you confirm.
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.
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. Preview shows your latest changes exactly as visitors will see them after publishing. The current live version is one click away in the same bar.