Skip to content

Menus

Reach for a managed menu for an external link, a heading-only item, or an order independent of the tree; linked items never go stale when a page moves.

Site navigation comes from one of two independent sources: the site tree itself, auto-derived from your content, or a managed menu you build by hand. Most sites need only the first; a managed menu exists for the shapes the tree can't produce.

What the tree gives you for free

Left alone, navigation is generated straight from content: any page marked nav-visible appears, filtered by its publish status and by any groups it is hidden from, in the order you've set for its siblings in the Site Tree. There's no way to slot in something that isn't a page, and no way to order it apart from reordering the tree.

Hiding an item from a group

On the Navigation tab, Nav Visibility by Group lists the site’s groups under Show in Navigation; untick a group and its members no longer see the page in the generated navigation. It applies only to this automatic tree, not to a managed menu or to breadcrumbs, which group visibility never filters. A person is hidden from an item if they are in any unticked group, and everything beneath the item goes with it. Visitors who aren’t signed in always see every item.

Only a signed-in person’s own session narrows the navigation; an API key or an OAuth client token reads the full, anonymous tree whatever groups its owner belongs to. Each translation has its own setting, with no fallback to the other languages.

What a managed menu adds

A menu is a separate, hand-built structure with its own item order, independent of how the content is arranged underneath it. It can hold two kinds of item the tree has no equivalent of: a link, pointing at either a page or an external URL, and a label, a heading with no destination — the column heading in a mega-menu, say. Reach for a managed menu when you need any of those: an external link, a label-only heading, an order that diverges from the page tree, or a curated subset rather than everything the tree would show.

Linked items self-heal

A menu item that links to a page doesn't store that page's URL — it looks it up live from the page's current address every time the menu renders. Move or re-slug the page later and the menu item follows automatically; there's nothing to fix on the menu side.

Deleting or unpublishing the target page isn't the same outcome. Delete it and the item is flagged broken — the editor shows an alert telling you to remove the item or turn it into an external link. Unpublish it and the item isn't broken at all; it's hidden from visitors — dropped from the rendered menu, along with anything nested under it — until the page is published again, which the editor reports as a status note rather than an alert. Nothing to fix there either — publishing the page is what fixes it.

For what moving or re-slugging a page actually does to its URL, see Slugs, paths, and moving a page.