The Sidebar Is Not A Graveyard

Open almost any docs site and you'll see it: a left sidebar with forty links, none of which tell you what you're looking at. The sidebar is where documentation goes to die — a flat, alphabetical graveyard of pages nobody navigates on purpose.

Navigation is an editorial decision, not an information-architecture exercise. The best docs don't list every page; they tell you what to read first, and what to read next. They read like a table of contents in a well-edited book, not a file tree.

Structure by journey, not by directory

Readers arrive with a goal — install it, migrate, ship something. Organize around those goals, and let the chapters flow. A developer reading "Getting started" shouldn't have to know which folder a page lives in to find the next one.

How to make navigation actually navigate

• Lead with a journey — Getting started, then the core concept, then the reference.
• Keep every sidebar short enough to scan in five seconds.
• Highlight the current page, and the next one, like a book's running head.
• Let search cover the long tail — don't list forty pages to be safe.

FOLIO's editorials typesetting does this by default: a table of contents that reads like a book, a live "next up" for every page, and search good enough that the sidebar never has to carry the whole library. A sidebar should be a guide, not a graveyard. Yours can stop being one today.