This article covers changes that the Page Builder introduces for editorial teams:
Topics covered here:
- Introduction
- Pages and folders
- Menus
- Navigation rules (named Link rules in the VSM)
- Context selection
Introduction
The VSM flexibility requires software engineers to help editorial teams set up the site structure based on business needs.
We've developed the Page Builder, which aims at streamlining the site structure's definition and maintenance. A new and easy-to-use and modern user interface lets editorial teams implement editorial strategies, requiring less administrator input.
Pages and folders
When crafting pages and folders, the Page Builder capabilities mirror the VSM ones, but within a modern user interface.
| VSM |
Exploring the site's structure |
| Page Builder |
Exploring the site's structure Filter tab not available: In the VSM, the Filter tab is where the redirect rules are set, managed by the legacy rendering engine. The Page Builder deprecates the legacy rendering engine, so the Filter tab is redundant.
Item Visibility tab not available: In the VSM, the Item Visibility tab allows you to set whether the site's structure import must either include or skip a page or a folder. This functionality is not yet available in the Page Builder, but it is planned for Q3 '25. For more information, read the article on managing pages and folders. |
Permissions
When setting permissions to pages and folders, the Page Builder capabilities mirror the VSM ones, but within a modern user interface.
| VSM |
Permissions at page and folder level |
| Page Builder |
Permissions at page and folder level For more information, read the article on adding authorization groups to pages. |
Variables
When setting variables to pages and folders, the Page Builder capabilities mirror the VSM ones, but within a modern user interface.
| VSM |
Managing variables |
| Page Builder |
Managing variables Variables path validator not available: When filling variables with paths, the path validator is no longer available. The path validator was tidily related to the legacy rendering engine, which is no longer maintained.
Allowed values for page parameters available in Page Builder 1.7.0: The ability to define the allowed values for page parameters — e.g., allowed values for the {slug} parameter of /mySite/{slug} page — is coming in mid-July '25. For more information, read the article on setting variables. |
URLs and aliases
When setting URL translations, the Page Builder capabilities mirror the VSM ones, but within a modern user interface.
Instead, only the Page Builder allows defining URL aliases, which improves SEO performance.
| VSM |
Managing URL translation
|
| Page Builder |
Managing URL translation and alias For more information, read the article on URLs and aliases. |
Static texts and images
Unlike the VSM that required creating stories and photos in the Content Manager and referencing them within dedicated modules, the Page Builder allows editorial teams to insert texts and images directly while designing pages.
In the screenshot below, a French text is part of the page's definition — find more information in the article on static texts.
Instead, in the example below, an image is part of the France page's definition — find more information in the article on static images.
Menus
When managing menus, the Page Builder capabilities mirror the VSM ones, but within a modern user interface.
| VSM |
Managing menus |
| Page Builder |
Managing menus Find more information on the article on menus. |
Navigation rules (named Link Rules in the VSM)
When managing menus, the Page Builder capabilities mirror the VSM ones, but within a totally new and improved experience.
Unlike the VSM, which manages Link Rules by page, the Page Builder lists all Navigation rules in a dedicated single page. This streamlines managing rules by ensuring a global visibility of rules scope.
| VSM |
Managing Link Rules |
| Page Builder |
Managing Navigation Rules Find more information in the article on navigation rules. |
Context selection
Unlike the VSM, the Page Builder allows ingesting custom templates, layouts, and modules — which we call contexts. Editorial teams choose which context to use when creating pages by selecting the corresponding Page Type.
For more information, read the article on creating pages.