Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Designing navigation and menus

How theme designers design navigation for a site whose structure editors change - menus built from the content tree, depth and width limits, the current page, breadcrumbs, sub navigation, small screens, and what to…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/theme-designers/designing-navigation-and-menus.md

On this page

Designing navigation and menus

This page is for theme designers who design the menus of a site. In most Exponential sites the main menu is not a fixed list in a template: it is fetched from the content tree, so it changes when editors add, rename, hide or reorder folders. A good navigation design works for the tree the site has today and for the one it will have next year. The template side is in Menus and navigation and Breadcrumbs.

Contents

  1. Where menus come from
  2. Designing for a tree that changes
  3. Depth
  4. The current page and the path
  5. Breadcrumbs
  6. Sub navigation
  7. Small screens and keyboards
  8. What to agree before drawing

Where menus come from

MenuUsual sourceWho changes it
Main menuchildren of the site's root node, filtered by class (often folders)editors, by adding, hiding or sorting folders
Sub navigationchildren of the current section's top foldereditors
Breadcrumbsthe path of the current nodefollows the tree
Footer linksa folder of links, or fixed template texteditors or developers
Utility links (sign in, language)template and settingsdevelopers

Ask which source each menu of the site uses. A menu fixed in a template can be designed to the pixel; a menu fetched from the tree must handle what editors do.

Designing for a tree that changes

  • Number of items. Draw the main menu with the current count, and with two more and two fewer. Decide what happens when items do not fit: wrap to a second line, move to a "More" menu, or switch to the small-screen menu earlier.
  • Label length. Folder names are written by editors and translated. Draw the longest label in the longest language of the site (Designing for many languages).
  • Order. The order follows the sort order editors set on the parent node. Do not design a menu that depends on a particular item being first or last.
  • Hidden items. Editors can hide a node, and the menu fetch normally leaves it out; nothing in the design should depend on a particular item existing.

Depth

Each level of a menu you design is a fetch, a cache and a test case. Most content sites need:

  • one level in the main menu;
  • the second level either in a dropdown or as sub navigation on the section's pages, not both;
  • deeper levels only in sub navigation and breadcrumbs.

Large "mega menus" are possible, but they are content as well: who maintains the groupings and the short descriptions? If the answer is "editors", the content model needs fields for it (Mapping a design to content classes).

The current page and the path

Mark both the current page and its ancestors: when a visitor reads an article inside "News", the "News" item in the main menu shows that they are in that section. The mark must not rely on color alone, and the current link carries aria-current="page" (Designing interactive states).

Breadcrumbs follow the node's path in the tree, which may be deeper and more technical than the menu. Decide:

  • whether the front page is the first crumb and how it is labeled;
  • how long paths shorten on small screens (often only the parent, as a "back to" link);
  • that the current page is the last crumb, not a link.

Sub navigation (a side menu of the current section) helps in deep sections. Design it for the section with the most children and for a section with none, in which case it should disappear rather than show an empty box.

Small screens and keyboards

  • At narrow widths the main menu moves behind a menu button. Design the open state, the close control and what happens to the second level (an expanding list is easier than nested panels).
  • Every level must be reachable with the keyboard, and dropdowns open on activation, not only on hover (Keyboard and focus).
  • The navigation is a landmark (nav with a label) and the menu button announces whether it is expanded (Landmarks and headings).

What to agree before drawing

  • To do: The source of each menu (tree, folder of links, template).
  • To do: Which classes appear in the main menu (usually folders only).
  • To do: The number of levels in each menu.
  • To do: How many items editors expect to add in the next year.
  • To do: Whether menus differ per siteaccess or language.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x