Act as a senior docs engineer. Build the documentation layout for {{business_name}} in my {{tech_stack}} project. Style: {{visual_style}}. Keep the existing content files and routing; this is the shell and components. Layout: - 1280: three columns: sidebar 260px, content at max 72ch, on-this-page rail 220px - 768: sidebar becomes a drawer behind a menu button; rail hides and becomes a disclosure under the title - 360: a top bar with menu and search; content with 16px gutters; no sideways scroll except inside code blocks The sidebar and rail scroll on their own, with sticky positioning under the header. Sidebar: sections as disclosure buttons with aria-expanded; the current page highlighted with aria-current="page" and scrolled into view on load; expanded sections remembered. Search: opens with Cmd or Ctrl+K and "/"; uses a real index (Pagefind for static sites, or Postgres full-text search, or the search service already in use); results grouped by page with the matched heading and a highlighted snippet; full keyboard support with visible focus; "No results" suggests related pages. Content components: - callouts (Note, Tip, Warning) with a text label and icon, not color alone - code blocks with a filename, language label, copy button announcing "Copied", and line highlighting - synced tabs for package managers or languages, remembered across pages - headings with anchors; scroll-margin-top under the sticky header - previous and next links, "Last updated", and "Edit this page" - breadcrumbs Type: body 16 to 17px, line height 1.65; code 14px in JetBrains Mono or the project's mono; h2 at 24px with a top border for scanning. States: a page with no headings hides the rail; search loading and errors; a 404 inside docs offers search. Motion: drawer 200ms; none under prefers-reduced-motion. Avoid: content wider than 80 characters, search that only matches titles, a sidebar that scrolls the whole page.