Working on a Redesign Without Taking the Live Site Down
Site branching lets you rebuild a site's pages in an isolated working copy while the live version keeps serving visitors unchanged.
You can now start a full redesign of a site inside Piskes Website Builder without touching what visitors see — branching, a feature that's unusual for a no-code builder aimed at small businesses, is live.
A branch is a working copy of a site's pages, created with one click from the site dashboard. Everything you'd expect to edit — layout, copy, sections, new pages — happens inside the branch, completely isolated from the version that's actually published.
What branches on purpose, and what doesn't
A branch is scoped to pages only. Your collections (products, blog posts, team bios, whatever structured content your site runs on), your uploaded assets, and your site-level settings stay shared between the branch and the main line. The reasoning is practical: branching a redesign shouldn't fork your blog, and a writer publishing an article while a designer reworks the homepage shouldn't have to decide which branch that article belongs to.
Merging when you're ready
When a branch is ready to go live, merging replaces the main line's pages with the branch's — wholesale, not word-by-word. There's no attempt at a line-by-line merge between two different redesigns of the same page, because that kind of automatic reconciliation tends to produce a page nobody actually designed. What makes a merge safe instead is that nothing is deleted: the version you're replacing is automatically parked as its own branch, so a merge you regret can itself be merged back.
Branches can be created and managed from the site dashboard, or by an AI assistant connected over MCP using the create_branch tool. Either way, the live site keeps serving the current pages the entire time you're working.