…section

Homepage & navigation
- New docs homepage (docs-home): developer-focused hero, ambient
  permission-graph animation echoing the SpiceDB pitch deck, a five-surface
  index, What's New + Releases, auto light/dark via Sandworm tokens
- Announcement bar restyled to the marketing terminal style: mono, sand-300
  accents, bracketed CTA, live (hourly-cached) GitHub star count, and a
  cli-spinners "hamburger" cursor that runs on load, rests, and reruns on hover
- Navbar logo shows "/docs"; primary CTA uses the Sandworm button style

Materialize
- Promote Materialize from a single concept page to a top-level section
  (getting-started / concepts / guides / api); update nav and inbound links

Fixes
- discovering-spicedb: HTTP/JSON reference pointed at SwaggerHub; now links to
  the local Swagger page (/spicedb/api/http-api)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Landing-page links 404'd under the deploy's basePath (/docs): the homepage
  used plain <a href="/..."> which Next doesn't prefix. Route internal links
  through next/link (external stay anchors) so basePath is applied.
- The home takeover made the navbar fully transparent (killed the blur bg), so
  scrolled content showed through it. Restore Nextra's themed navbar background;
  only soften the border.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Fold Best Practices into SpiceDB (content is SpiceDB-specific) — drops the
  index from five surfaces to four; BP now a SpiceDB sublink
- Rename the AuthZed surface to 'Managed SpiceDB' (bare 'AuthZed' read as
  corp info; pairs with open-source SpiceDB above it) — ENTRIES + _meta.ts
- Promote 'Book a demo' from the page TOC to the top nav (persistent
  conversion vs lost beside a short TOC); rail keeps the Cloud self-serve CTA

Physical /best-practices -> /spicedb move + redirect left as a follow-up
(needs an SEO redirect for the indexed URL).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The banners + /changes page must never ship to the live docs. Gate on
NODE_ENV/VERCEL_ENV so it shows in local dev and Vercel preview builds only:
- production build emits an empty manifest (no banners, empty data)
- /changes returns notFound() in production (route not publicly reachable)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Fixes the 'Lint Everything' (oxfmt --check) CI failure across the branch's
new/changed files. Pure formatting, no behavior change.

There was a public/favicon.ico but nothing linked it, so no <link rel=icon>
was emitted and the /docs basePath meant the browser's root /favicon.ico
request never hit it. Move it to app/favicon.ico so Next auto-emits a
basePath-correct icon link.

- Nextra accent hue 45 -> 28 so links/active-nav read as Sandworm sand, not gold/yellow
- Docs Index sublinks stay open (no hover-collapse) so the sub-navigation is visible at a glance
- Each surface's index number takes its own accent color (SpiceDB magenta, Managed SpiceDB teal, Materialize violet, MCP blue) to color-code the surfaces

The color prop only set hue+saturation, so the accent rendered at Nextra's
default lightness — a muddy orange, not sand. Add explicit lightness so the
docs-page accent (links, active nav, highlights) equals sand-300 exactly in
dark (28 100% 72%) and a readable darker sand step in light.

Replace the ✅/❌ emoji in feature tables with <Yes/> / <No/> components
that mirror the marketing pricing comparison: a teal→violet gradient disc
with a dark Lucide check, and a red-outlined disc with a red Lucide x. Inline
Sandworm colors (no new dep). Registered globally in mdx-components.

The Yes disc used the bright dark-mode Sandworm gradient, which washed out on
white table cells. Move styling to feature-icon.css with a light/dark split:
light gets a deeper saturated teal→violet disc + white check (pops on white);
dark keeps the brighter gradient + dark check.