Menus and addresses
Menus
A menu is a tree of links, per organization. Items can point at a record, a listing, an external URL or nothing at all — a parent that only groups its children.
Each item can carry an icon, a CSS class and conditions, so the same menu can show different things to different visitors.
The item matching the current page is marked active, and so is its parent chain. Styling that is a matter of CSS, not of building a second menu.
Addresses
Where a thing lives is answered in one place. An alias an editor typed, a rule that gives a whole content type a pattern, a type whose public page is not the record page — all of them resolve through the same answer.
Never assemble a URL by hand
Not in a template, not in a token, not in a block. A hand-built address is correct until the day the type gains an alias, a pattern or its own kind of page — and then it is quietly wrong, still linking, still returning something. Ask for the canonical address.
Patterns
A content type can be given an address pattern built from its own values —
products/[record:field:category:path]/[record:field:sku], for instance.
Patterns use tokens, so an address can follow a
category hierarchy without anybody maintaining a list.
Redirects
When an address changes, the old one should keep working. Redirects are per site, and a moved page can be sent to its new home permanently or temporarily.
Meta tags
Titles, descriptions, canonical links and social-preview cards, defined per content type with tokens and overridable per record.
A feed and a sitemap follow the same visibility rules as everything else: what is not published is not in them.