When to use
- Documentation sections — a sidebar of the other pages in the section. The TOC answers "what is on this page"; this answers "what else is in this section".
- Every page in a section — the same block works unchanged on each one, because it works the section out from the URL.
Skip it for a section with a single page. With fewer than two links the block renders nothing.
Key decisions
- Source: the list comes from the site navigation, in its authored order — not the query index, which is alphabetical and cannot tell the overview from the rest. To add a page to the sidebar, add it to the nav group.
- Section override: leave it empty to show the current page's section. Set a path such as /operations to show another section.
- Placement: a 25% Column beside the content, like the TOC. Sticky on wide screens, inline above the content on phones.
How the section is matched
A page's section is the first segment of its path, so /operations and /operations/onboarding show the same sidebar. The block then finds the nav group whose links live in that section, so the grouping in the nav — not a naming convention — decides what belongs together.
The header already fetches the nav on every page, so the sidebar costs no extra request, and the current page is known from the URL, so it is marked on first paint.
All authoring options
General
title: heading above the list. Default "In this section"
rootPath: section override, e.g. /operations. Empty uses the current page's section
Analytics
classes_track-inview: emit an event when the block scrolls into view
classes_track-link-click: emit an event, with the target path, when a link is clicked
meta: block-level analytics meta, sent as a JSON string
Events emitted:
emu-section-nav:inview
emu-section-nav:link:click