Use page branching to build and ship faster with multiple designers.
Page branching lets multiple designers work on different pages on the same site at the same time, enabling large teams to build and ship updates faster. When you branch a page, you take a “snapshot” of one of the pages on your site, which lets you safely explore new design changes without affecting the original. Once you’re happy with your changes, you can merge your page branch into the main site to overwrite the original page.
In this lesson, you’ll learn:
With page branching, you can work on a single page’s design while other designers work on other page branches or the main site. After you’re done designing, you can merge your page branch to overwrite the original page’s design on the main site.
Changes on the main site won’t impact page branches unless you specifically decide to pull updated classes, components, and interactions from the main site into your branch. Changes on page branches won’t impact the main site until the branch is merged back into the main site.
Anyone with Designer access (i.e., Site admin, Can design & publish, Can design, Can design (limited)) can create and merge branches. Learn more about site level roles and permissions.
You don’t need design control to branch a page — in fact, a designer can be working with design control on the main site while other designers work on page branches. However, you will need to have or request design control to merge a page branch, or you can ask your teammate with design control to merge your branch for you.
Full-site publishing isn’t blocked by page branching. Anyone with design control can publish the main site without publishing the branches — your branches are a safe space to work. To publish your page branch, you’ll need to first merge it into the main site.
The types of site pages you can branch include:
To create a page branch:
The page branch will open in the Designer and you can start designing. Your teammates will see your new page branch when they refresh the Designer.
Editing a page branch is just like editing a page, with a few differences.You can only have 1 designer working on a page branch at a time. If your teammate wants to work on your page branch, you’ll have to navigate to a different page first.
Additionally, you can only have 1 branch per page at a time. If you want to create a new branch for a page, you’ll need to merge or delete any existing branch first.
If a class, component, or interaction is used on the main site as well as the page branch, and is changed on the main site, you’ll see the impact of these changes on the page after merging your branch — they won’t immediately appear on the branch.
However, you can check for updates to classes, components, and interactions on the main site and pull those into your branch at any time. We recommend frequently pulling these updates into your page branch to ensure you’re designing with the latest classes, components, and interactions from the main site.
Important: You can copy and paste between pages and branches. However, if you paste an element into a branch that has classes that have been modified on the main site, the version of the classes that exist on the branch will take effect. The main site’s classes won’t be affected.
To check for class, component, and interaction updates on the main site:
If any classes, components, or interactions were updated on the main site, a modal window will pop up to allow you to pull updates from the main site. To pull updates from the main site into your branch, click Pull updates. Then click Okay on the branch update confirmation modal window.
You can also choose to pull updates later by clicking Update later on the modal window.
If there are no class, component, or interaction updates on the main site when you check for updates, a modal window will pop up explaining that there are no updates to pull into your branch. You are working with the latest designs from the main site. You can click Okay to close the modal window.
Page branches share the same CMS as the main site, so any changes made to the CMS while a page is branched will appear on the page branch. For example, if a Collection list initially has 4 items when you create a page branch, and you add another item to the Collection from the main site, the CMS will then show 5 items in the page branch Collection list.
If a designer leaves a branch, any other member of the Workspace who has design access can take over the branch to edit, merge, or delete it. For example, if designer A leaves the branch, designer B can take over (as long as designer A is not actively working on the branch at the same time).
When you’re finished with your design, you can share a read-only link with other members of your team before merging the page branch. Learn more about sharing a read-only link.
You can view class-creation activity on page branches from the Site Activity log. Learn more about the Site Activity log.
Once you’re done designing your page branch, you can merge your branch back into the main site. Your teammates will see your merged page branch when they refresh the Designer. Note that merging the page branch will overwrite the original page on the main site, so make sure you’re happy with your design before merging.
Important: Any changes made to the content of the original main site page while it was branched will be lost after you merge your page branch. Changes to components, classes, or interactions will not be lost. We don’t recommend making changes to the original main site page if it has a page branch.
There are 2 ways to merge your page branch changes into the original page:
To merge your changes from the page branch:
To merge your changes from the Pages panel:
You can delete a page branch if you decide to keep the original page design, or if you want to start a new page branch. To delete a page branch:
If you accidentally delete a page branch but want to view the branch’s design or fully restore the branch to your site, you have a couple options. You can either preview the page branch’s design in a site backup by clicking the backup’s “Preview” button, or fully restore the page branch from a site backup by clicking “Restore.” Restoring a site backup will restore both the main site and page branches to their state at the time stamp.
Important: Please be aware that when you perform a restore from a site backup, all CMS Collection and item IDs will refresh. Learn how to preview or restore a site backup and what happens when you restore a site backup.