Branching, Previewing, and Merging a Content Change, Step by Step

A follow-up to the branching feature we announced separately: here's the actual sequence for taking a change from idea to live using a site branch.

1. Create a branch

From the site dashboard, start a new branch and give it a name — "Fall promo redesign," "New pricing page," whatever describes the change. This copies every current page into an isolated working set; your collections and site settings aren't touched. You can also do this by asking a connected AI assistant to run the create_branch MCP tool instead of clicking through the UI.

2. Edit inside the branch

Open any page in the branch and it opens in the same page editor you already use for the main site — same drag-and-drop canvas, same blocks, same save behavior. Nothing about editing a branched page is different from editing a live one, which is deliberate: there's no separate "draft mode" interface to learn.

3. Preview before merging

Because a branch is a real, isolated set of pages, you can review the whole redesign in context before anyone else sees it — no partial states, no half-applied changes leaking onto the live site while you work.

4. Merge

When you're satisfied, merging the branch replaces the main line's pages with the branch's pages. This is a full swap, not a diff — the branch wins outright on every page it touched. The version being replaced isn't deleted; it's automatically set aside as its own branch, so if the merge turns out to be wrong, merging that backup branch back restores exactly what was live before.

An AI assistant with the create_branch write permission can start step 1 on your behalf; steps 2 through 4 currently happen in the editor itself.