Undo Anything: Version History and Rollback in C Building

The hardest part of editing a website isn't the editing. It is the worry that one change will break something and you won't know how to get back.

C Building is designed so that you can always get back. There are two safety nets: one for the site you are working on, and one for the site your customers see.

Safety net 1: version history while you edit

As you work, C Building saves versions of your website, for example after each round of AI edits and each time you publish. Open the version history in the editor and you can restore the site to any of those earlier states.

That changes how it feels to edit:

• Try a bold change. Ask the AI for a completely different look for your home page. If you don't like it, restore the version from before.
• Undo a chain of edits. If a few changes in a row took the page somewhere you didn't want, go back to the last version you liked instead of undoing each one.
• Recover from a mistake. Deleted the wrong section? It is still in an earlier version.

Version history covers edits made in both ways, by chatting with the AI and by clicking on the page yourself, because both change the same website.

Safety net 2: nothing goes live until you publish

Editing and publishing are separate. Everything you change in the editor stays in your working copy until you press Publish, or Update for a site that is already live. Your customers keep seeing the last published version while you experiment.

So you can:

• Work on a new menu over several days without customers seeing it half-finished.
• Check the result on different screen sizes in the editor before anyone else sees it.
• Publish only when you are happy.

Rolling back the live site

Sometimes you only notice a problem after publishing: a wrong price, a missing phone number, a photo that looks off on phones. Every publish is recorded, and the publish history lets you roll the live site back to the previous release while you fix the working copy.

If you need the site offline for a while, for renovation or a seasonal closure, you can also take it offline from the project's Domains page, and publish again when you are ready.

Why we built it this way

Why keep editing and publishing separate?

Because a small business website is live all the time. Customers look it up at midnight. Separating the two means the version they see is always one you chose, never one you are halfway through changing.

Do I need to save my work?

No. Your edits are kept as you go, and versions are saved along the way. Publishing is the only step that needs a decision.

Can the AI undo its own changes?

You don't need to ask it to. Restore the version from before the AI's edit, and you are back where you were.

Wrapping up

Being able to go back is what makes it safe to try things. With version history for your work in progress and publish history for your live site, any change on a C Building website can be undone. More on why this matters in why we replaced our block editor with editing on the page.