Reading the layouts

Each template below is a Python function in components/layouts.py that assembles a full HTML page from fragments (headers, sidebars, body_html, etc.). Names like showcase_page map to those functions.

Canonical doc shell

showcase_page is the canonical layout for generated static documentation in sibling projects. Use generator/build-showcase.py as the reference for how to call it. The other layouts below are legacy or specialized (landing/hero, gallery grids, split panels, blueprint handbook/chapter/product shells)—use them only when you have a specific need.

What the schematic shows

  • Wireframe diagrams (below each section) are static SVGs — they only illustrate region names.
  • Open live preview loads a real built page inside an iframe in the modal, with a short region legend on the right.
  • Showcase, landing, and gallery reuse existing pages (tokens.html, index.html, diagrams.html); split, handbook, chapter, and product use generated preview-*.html files from the build.

showcase_page

Documentation reference layout: unified sticky header + sidebar + content + optional right-rail ToC. This is the primary layout for component documentation sites.

How the regions connect

  • Top: sticky site header (brand + breadcrumb + page title).
  • Left: scrollable sidebar below the header.
  • Center: main article column (body_html).
  • Right: optional ToC (toc_html); omit for two-column layouts like gallery.
Static schematic: showcase_page
Embeds a real example page in the modal (iframe). Diagram above is a static wireframe only.
ParameterTypeDescription
browser_titlestrHTML <title> value
page_titlestrVisible H1 in header bar
sidebar_htmlstrSidebar navigation markup
body_htmlstrMain content area HTML
toc_htmlstrRight-rail table of contents (optional)
extra_cssstrAdditional inline <style> block
extra_jslist[str]Paths to extra JS files

Used by

Kitchen Sink showcase mini-site (this site) — canonical reference for external generators

landing_page

Full-width hero page with no sidebar. Ideal for homepages and overview pages.

How the regions connect

  • Vertical stack: no left sidebar; content uses full width.
  • Nav is a single top bar; hero and body are separate slots.
Static schematic: landing_page
Embeds a real example page in the modal (iframe). Diagram above is a static wireframe only.
ParameterTypeDescription
browser_titlestrHTML <title> value
hero_htmlstrHero section content
body_htmlstrBody content below hero
nav_links_htmlstrTop navigation bar links
footer_htmlstrFooter HTML (optional)

Used by

Kitchen Sink landing page

split_page

Sidebar + two-panel content: live example on the left, documentation on the right. Stacks vertically on mobile.

How the regions connect

  • After the shared header + sidebar, the main area splits into two columns.
  • Left: demo / preview; right: prose or API docs.
Static schematic: split_page
Embeds a real example page in the modal (iframe). Diagram above is a static wireframe only.
ParameterTypeDescription
browser_titlestrHTML <title> value
page_titlestrVisible H1 in header bar
sidebar_htmlstrSidebar navigation markup
left_htmlstrLeft panel (example / preview)
right_htmlstrRight panel (description / code)

Used by

Available for component detail pages

handbook_page

Auto-generated handbook page with 3-column layout (sidebar, content, ToC). Used by blueprints-website.

How the regions connect

  • No separate “site header” band: sidebar and main start at the top of the viewport.
  • Three columns: nav | article | section ToC.
Static schematic: handbook_page
Embeds a real example page in the modal (iframe). Diagram above is a static wireframe only.
ParameterTypeDescription
browser_titlestrHTML <title> value
page_titlestrVisible H1
sidebar_htmlstrSidebar navigation markup
body_htmlstrMain content (from Markdown)
toc_htmlstrRight-rail ToC

Used by

blueprints-website (bpw)

chapter_page

Hand-crafted methodology chapter layout with JS-driven sidebar. Uses docs-theme.css.

How the regions connect

  • Same 3-column grid as handbook; the schematic is shared.
  • Difference: sidebar markup is filled by client-side JS (nav JSON), not only server HTML.
Static schematic: chapter_page
Embeds a real example page in the modal (iframe). Diagram above is a static wireframe only.
ParameterTypeDescription
browser_titlestrHTML <title> value
page_titlestrVisible H1
sidebar_htmlstrChapter sidebar markup
body_htmlstrChapter content

Used by

blueprints-website methodology chapters

product_page

Product / marketing layout with tier-grouped sidebar. Uses forgesdlc-theme.css with fs-* classes.

How the regions connect

  • Mobile-first: optional top bar triggers offcanvas on small screens.
  • Desktop: tier-grouped sidebar + wide article column (different theme classes than Forge docs).
Static schematic: product_page
Embeds a real example page in the modal (iframe). Diagram above is a static wireframe only.
ParameterTypeDescription
browser_titlestrHTML <title> value
page_titlestrVisible H1
sidebar_htmlstrProduct tier navigation
body_htmlstrProduct page content

Used by

forgesdlc.com (forge)

Layout