Reordering pages and nesting navigation

Documentation / Pages and navigation

Navigation ordering and nesting come from a stored tree. Page metadata supplies labels and visibility. Renaming a URL or changing a page title does not, by itself, move a page into a different branch.

Arrange the tree

Open the intended collection in the content area. Where the drag-and-drop tree is available, move a page before or after another page to make it a sibling, or into the child position to nest it. A branch moves with its descendants. The tree prevents placing a page inside its own descendant.

The dedicated reorder view also provides Move up and Move down for swapping pages within the same sibling group. Those arrows do not change the parent. Save the reordered structure using the view's save control rather than assuming a changed on-screen order is already persistent.

Keep the main navigation understandable before adding several nested levels. A documentation collection and the main menu can have different structures and should be reviewed independently.

Check structure and visibility

After saving, reload the collection to confirm the hierarchy persisted. Open the public navigation on desktop and mobile, and check each moved page's resolved address. Parent placement can contribute to a nested route.

A page can exist in the root structure and still be absent from public navigation. Availability, the listing choice, future dates, and system-page exclusions can remove it from the visible menu. Review those settings before trying another reorder.

Do not store page titles or access information in the tree itself. They belong to the individual page.

For collection-specific trees and URLs, see Collections and content trees.