Markdown versions of all docs pages are available by appending .md to any docs URL.

How wide the sidebar, content, TOC, and navbar are, what each pane’s width comes from, and where the breakpoints that hide them live.

The docs page is a horizontal row of up to three panes — left sidebar, center content, right table of contents (TOC) — inside a wrapper capped by page.width. The navbar above it is capped separately by navbar.width, which should normally match page.width; see the note at the end.

The panes, at a glance

    block-beta
  columns 24
  sidebar["Sidebar<br/>256px<br/>visible ≥1280px"]:4
  content["Content<br/>≈672–832px of readable text<br/>(1152px cap, rarely reached)"]:16
  toc["TOC<br/>256px<br/>visible ≥1024px"]:4
  

This is drawn to the proportions of a 1440px (page.width: wide) viewport with both rails visible. It is not to scale below xl (1280px), where the sidebar stops being persistent — see Breakpoints.

Where each width comes from

The content cap rarely binds in practice: at any page.width up to wide (1440px), subtracting the sidebar and TOC leaves less room than the 1152px cap, so the real constraint on content width is the wrapper width minus the rails, not the cap itself (see the worked numbers below). The cap only takes over on very wide viewports with page.width: full.

Worked numbers by page.width

Assuming both the sidebar and TOC are visible (viewport ≥1280px) and content carries its own hx:md:px-12 (48px each side) padding:

So a hoped-for “content pane ≤800px” holds at page.width: normal (≈672px) but not quite at wide (≈832px) — wide is what agentgateway-oss-website and the docs hub’s agentgateway product both use.

Breakpoints

Note the TOC and sidebar do not share a breakpoint in this module: between 1024px and 1279px the TOC is visible but the sidebar is drawer-only, which is a deliberate divergence from vendored Hextra (where both use xl).

Keep navbar.width matching page.width

The navbar and the content wrapper are two independent settings — params.navbar.width and params.page.width — and nothing enforces that they agree. If they diverge, the navbar’s logo drifts out of alignment with the sidebar below it as the window resizes. Until this module’s [Unreleased] fix (see CHANGELOG.md), navbar.width was silently discarded and the navbar always rendered at the wide default regardless of what a consumer set — worth knowing if you’re diagnosing an older pinned version.