Give the docs viewer a single scroll context

[BeckettFrey]

Closes #15.

The nesting

public/docs is a pdoc bundle — already a complete docs site, with a sidebar
pane and a content pane that scroll independently by design. The route wrapped
it in two more scroll contexts:

window            ← scrolled, because <Footer> sat outside the h-screen block
└ iframe card     ← inset by pt-24/pb-8 + rounded border, so it scrolled early
  ├ pdoc nav      ┐ the two pdoc actually intends
  └ pdoc main     ┘

The window layer was the worst of it: <Footer> was a sibling after a
h-screen overflow-hidden div, so the document ran a full viewport plus a
footer. Scrolling to reach the footer slid the entire docs card off-screen
while the docs themselves stayed put.

The fix

Give the bundle the whole viewport under the navbar and drop the Footer from
this route, so the only scrollbars left are pdoc's own two. The window can no
longer scroll at all.

• app/docs/page.tsx — full-bleed frame; Footer removed.
• app/globals.css — body forces overflow-y: scroll site-wide to avoid
  layout shift. On a page that fits the viewport exactly there is nothing to
  shift and nothing to scroll, so that renders a second, dead scrollbar beside
  pdoc's real one. Added a body:has([data-full-viewport]) opt-out.

Two things fixed along the way:

• Frame points at voxkit.html directly. /docs/index.html is only a
  <meta http-equiv="refresh"> stub. In a frame that hop becomes a session
  history entry, so leaving /docs took two Back presses — the first bounced
  you straight back into the docs.
• Renders on the server now. The page carried "use client" but held no
  client state, so it gets real metadata (it previously inherited the generic
  site title). Still prerendered — ○ /docs in the build output.

Verified

lint, typecheck, format:check and next build pass; /docs confirmed in
a browser against a production build.

Not in scope

• layout/Navbar.tsx:20 is position: fixed with no top-0, so it renders at
  its static position and only lands at the top when it is the first child of an
  unpadded parent. This route follows that convention, but it is a trap worth
  hardening separately — top-0 would be a no-op for all five current pages.
• Docs pages still are not deep-linkable: navigating inside the frame does not
  update the address bar. Left for the reimplementation the issue anticipates.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
voxkit-web	Ready	Preview	Aug 20, 2026 5:42pm