Pages & navigation
Structure lives in the hub and on the header nav widget — not a separate admin site.
Who: Pages is admin (and anyone granted it). Editors who lack Pages still edit content on pages they can open — they will not see the Pages hub item.
Pages (site map)
Hub → Pages opens the site map:
- See slugs, titles, and visibility.
- Create or open pages.
- Set page visibility per row:
| Visibility | Who can view |
|---|---|
| Public | Everyone (including guests) |
| Editors | Editors and admins |
| Admin | Admins only |
| Nobody | Hidden from normal browsing (keep the page without exposing it) |
New pages get a normal public URL under your site host. There is no draft/publish toggle for everyday CMS work; visibility decides who can see the page. Staff CRUDs stay Editors or Admin and are linked from Hub → Records, not the visitor menu.
Widget visibility
Hub → Site → Enable grants turns on visibility on each armed section (Public / Editors only / Admin only). That is per widget, separate from the page’s visibility. Both must allow the viewer for the block to show.
Nav (menu tree)
The header menu is a Navigation widget. Use that section’s Content handle (tree editor) — not a hub slide:
- Add, nest, reorder, rename, and remove menu items.
- Point items at pages (or external URLs where supported).
In-page Cards (a grid of links to other pages) use the same Navigation widget on the page canvas, with template Cards — not a listing of records and not a handmade HTML grid. Layout + offers Navigation; the header menu stays a separate bar. Pick pages in the tree; label and blurb copy from the page unless you override them in the tree. Tile images are optional.
SEO / sharing cards
Hub → Pages has no SEO or Open Graph fields today. For link previews and descriptions, ask the assistant, or override card label / blurb in the nav tree for Cards tiles. Do not expect a Pages SEO form.
Tips
- Create the page in Pages, then link it in Nav.
- Empty new sites: create a page first so Layout has somewhere to stand.
- Footer or secondary menus, when the theme exposes them as Navigation, use the same Content-handle tree as the header.
- After you enable a pack, placement offers in edit chrome suggest where to place its widgets. Authors own pages and nav — packs do not invent staff menus for you.
- Every Navigation widget is shared (one tree for the site).