Sitemap versions
Try another structure without touching the current one, compare versions, send one for review, lock it and make it the main version.
A sitemap version is an alternative structure for the same site. Jenny's Pet Supplies might keep Main as the live plan while trying a Redesign where Dog Food, Cat Food and Toys move under a new Shop by Pet page.
What a version keeps, and what it shares
Each version has its own structure: which pages it has, where they sit (parent, region and order), and their title, slug, page type, colour and notes.
The content is shared. A page that is in two versions is the same page: its blocks, SEO, metadata, translations, status, assignees, due date and comments are the same in both. Editing the content of "Dog Food" from either version changes it for both.
- A page you add in a version exists only in that version until you make it main.
- A page you delete in a version stays in the other versions that have it.
Switch versions
The version menu sits next to the project name at the top of every project screen. It lists every version with its page count and state. Choose one to open its sitemap; the address ends in ?version=…, so you can bookmark or send it.
While you look at a version other than main, the sitemap says so. The content overview, calendar, search, My work, share links, the public API and the Drupal package always use the main version.
When you open a page's content from a version's sitemap, the editor shows that version's title and slug, and a note that the content is shared.
Create a version
Project managers choose New version from… in the version menu. The new version starts as a copy of the structure you are looking at (for example "Redesign v2", copied from Main). Move, rename, add and delete pages in it as usual: none of it changes the version you copied.
Compare versions
Choose Compare versions, then pick the two versions. PagePot lists the pages that were:
- Added or Removed
- Moved to another parent or region
- Renamed
- Reordered among their sibling pages
Choose Highlight on the sitemap to see the changes on the map: changed cards get a coloured outline and a label. A note at the top counts the changes (removed pages aren't on that map) and Details lists them. Close the note to stop comparing.
Review, approve and lock
Project managers move a version through its review:
- Submit for review: the other project managers are notified. The version shows "In review".
- Approve (or Return to draft): the person who submitted it is notified.
- Lock: the structure becomes read-only for everyone. Content can still be edited, because it is shared.
Unlock returns a locked version to the state it had before (for example Approved). An approved version can still be changed: lock it if nobody should.
Make a version main
Make main turns a version into the main one. PagePot shows how it differs from the current main version before you confirm. Nothing is copied or deleted: the old main stays in the list as an ordinary version, so you can switch back later. Pages only the old main had drop out of the content overview until you make it main again.
Rename and delete
Rename changes a version's name (locked versions too). Delete removes a version other than main, and not while it is locked. Pages that only that version has are deleted with their content; PagePot names them before you confirm. Share links to the version stop working.
Export and share a version
- In Export → Sitemap, choose the Version to export (PDF, PNG, CSV, outline or XML).
- In Project settings → Sharing, a whole-project link can show a chosen version. Links left on "Main" follow whichever version is main.
Test versions with users
On the Pro plan and above, a tree test can compare up to three versions: each participant tries the same tasks in one version, and the results show which structure people find things in.