--- title: "Feature: Navigation" manual: "Frontend Theme for Extension Development" version: "main" source: "Changelog/2.0/Feature-Navigation.rst" modified: "2026-09-17T04:52:50+00:00" --- # Feature: Navigation ## Description The theme now renders its **three navigations**: a main menu, a left-hand sub navigation for the current section, and a breadcrumb trail. All three are the same core `MenuProcessor`, configured three different ways, in `Configuration/TypoScript/Navigation.typoscript`. | Navigation | Source | Rendered on | | --- | --- | --- | | Main menu | Site root, two levels | every page, in the header | | Sub navigation | The current page's **section**, two levels | the **Content page with sidebar** layout only | | Breadcrumb | The rootline, root to current page | **Content page** and **Content page with sidebar** | ## The sub navigation fixes a rootline position, not the current page The sub navigation is configured against the current page's **first-level ancestor**, not the current page itself, using `special.value.data = leveluid:1` rather than `entryLevel`. The difference matters because it is easy to get backwards, and the wrong choice looks correct in the one place it is checked first. `entryLevel` is relative to the current page's *depth* \- the same value resolves to a *different* ancestor on a second-level page than on a third-level page. `leveluid:1` instead indexes the current page's rootline directly: index `0` is always the site root and index `1` is always the first page below it, on every page regardless of how deep it is. That is what keeps the sidebar showing the same section three levels down as it does on the section's own landing page, rather than emptying out underneath it. A sub navigation built from the current page's own children looks entirely correct on a first-level page - there, the section root *is* the current page - and only fails on the pages below it, exactly where a reader needs the navigation most. `Tests/Functional/NavigationRenderingTest.php` therefore runs against a fixture three levels deep and asserts the same section content at all three, rather than stopping at the depth where the bug would already be invisible. ## Placement follows the backend layout Each navigation is its own numbered TypoScript key (`page.10.dataProcessing.10/.20/.30`), so a site package can remove exactly one without touching the others: ```typoscript page.10.dataProcessing.20 > ``` The sub navigation is rendered only on the **Content page with sidebar** layout - the one layout with a left column, per [Backend layouts decide the page template](Feature-BackendLayouts.html#feature-backend-layouts). Choosing that layout in the page module is how an editor asks for the left navigation; there is no separate flag. The breadcrumb renders on **Content page** and **Content page with sidebar**, and deliberately not on **Start page** (no trail is worth showing there) or **Default** (the bare layout, which is also the one layout that already renders the page title itself). ## Accessibility - Every `