Pages are stored in the system using a hierarchical structure. The structure is presented as a tree in the Manage Pages user interface.
Access the Manage Pages dialog using the icon in the Admin Toolbar, the vertical toolbar on the left side of the screen.
The following actions can be performed from the “Manage Pages” dialog.
Deletes the selected page or folder from the system.
Moves the selected page or folder up in relation to its siblings. This will affect the order of pages in the banner.
To reparent a page or folder to a different folder, you can either “edit” the page or folder and select a new parent folder or drag and drop the page or folder within the tree.
Moves the selected page or folder down in relation to its siblings. This will affect the order of pages in the banner.
Editing a page exposes where the pages resides on the system, as well as how it is presented within the navigation system.
It is important to note that the folder system used here has implications when provisioning content. If groups of users can be granted access to groups of content, it makes the provisioning process a lot easier. As such, the structure used for organizing content should reflect how different groups will access the content.
The page name is what will appear in the navigation menu.
This property determines whether a page (or folder) is directly accessible through the navigation menu. The navigation menu is represented by tabs in the banner of the user interface. If a page is hidden, then it will not appear as a tab.
This represents where a page physically resides on the system. This physical location has two separate implications.
When moving a page or folder from one folder to another, the system will prompt for confirmation about whether it should move associated provisioning configuration. Note that the provisioning configuration that is affected is only that relating to the specific item (page or folder) being moved, and in the case of a folder, also any children of that folder. So a page or a folder that is not explicitly provisioned to a domain, but is implicitly provisioned due to an ancestor folder being provisioned, may end up being not provisioned, if it is moved to a folder that is not already provisioned.