A menu is either drawn from the page tree, so it cannot fall out of step with the site, or built by hand where the order is editorial. Either way the markup is yours and the current page marks its own link.
Talk to us about your navigation →A menu draws from the page tree, or from items you write by hand. Tree menus follow the site; hand-built ones follow you.
A skin is the markup a menu renders: a wrapper, an item fragment per level, and the panel that holds the level below. It is your HTML, not a framework’s.
Three classes are applied as the menu renders, so the current page, its ancestors and any item with children can style themselves without a line of JavaScript.
A menu can carry its own stylesheet and script, published as ordinary code pages under styles/ and js/.
The editor lists every template, layout and page rendering this menu — and saving republishes them, because a menu change is a change to every page that carries it.
One search across pages, assets, objects and people, so finding a thing does not require knowing which tool it lives in.
A demonstration installation, with invented data.
Hand-maintained navigation is where sites rot: a page is renamed, moved or retired, and the menu still points at the old one. A tree-driven menu is derived from the structure, so renaming a page renames its link and moving it moves its link.
Where the order genuinely is editorial — a footer of chosen links — build it by hand. The tool supports both because sites need both.
An imported site usually arrives with its navigation as static markup: real HTML, real hrefs, no awareness of the page tree. It can be converted into a real menu without giving up its markup, because the skin is the markup.
So a redesign does not have to start by fighting a menu component that insists on its own classes.
Navigation that follows the site.
If your menu and your sitemap disagree, one of them is lying to your visitors and the other to Google. Get in touch →
