Follow-up to #174. The "How MateMate Works" hub landed in PR #176 (docs/index.html — two question-based entry cards → architecture / the-fleet). What remains to fully "knit the pages into one site" is a shared cross-page top-nav on the two deep pages so a reader can move between them (and back to the hub) without relying on footer links.
What's needed
A light sticky top-nav — ♞ MateMate (→ hub) · Overview · What is it? · How it was built? — with the current page marked, added to:
docs/architecture/index.htmldocs/the-fleet/index.html
Both pages are self-contained, so the nav must be themed with each page's own design tokens and adapt to their theme systems (architecture: light/dark + the cultural themes added in #181; the-fleet: the cultural lineage themes from #179). On mobile the nav must coexist with each page's fixed theme-switcher dial (e.g. drop the dial below the nav).
Why it's split out
These two files are under active concurrent redesign — the cultural theme switcher was rolled across them in #179/#181, and a shared-nav PR against them conflicted repeatedly. This is best done in coordination with whoever owns that theme-switcher rollout (the natural home for a cross-page nav), or once the docs settle.
Reference implementation
A working, per-page-themed version of exactly this nav was built and verified (renders + adapts across themes incl. light, links resolve, mobile dial relocation) on branch claude/clever-kapitsa-57c6a3 at commit 5a24bee — see the +37-line .sitebar nav added to docs/the-fleet/index.html and the nav retrofit in docs/architecture/index.html there. It can be lifted/adapted rather than rebuilt.
Done = both deep pages carry the shared nav, themed natively, links resolve, mobile-safe, PII-clean, still self-contained.
Follow-up to #174. The "How MateMate Works" hub landed in PR #176 (docs/index.html — two question-based entry cards → architecture / the-fleet). What remains to fully "knit the pages into one site" is a shared cross-page top-nav on the two deep pages so a reader can move between them (and back to the hub) without relying on footer links.
What's needed
A light sticky top-nav —
♞ MateMate(→ hub) · Overview · What is it? · How it was built? — with the current page marked, added to:docs/architecture/index.htmldocs/the-fleet/index.htmlBoth pages are self-contained, so the nav must be themed with each page's own design tokens and adapt to their theme systems (architecture: light/dark + the cultural themes added in #181; the-fleet: the cultural lineage themes from #179). On mobile the nav must coexist with each page's fixed theme-switcher dial (e.g. drop the dial below the nav).
Why it's split out
These two files are under active concurrent redesign — the cultural theme switcher was rolled across them in #179/#181, and a shared-nav PR against them conflicted repeatedly. This is best done in coordination with whoever owns that theme-switcher rollout (the natural home for a cross-page nav), or once the docs settle.
Reference implementation
A working, per-page-themed version of exactly this nav was built and verified (renders + adapts across themes incl. light, links resolve, mobile dial relocation) on branch
claude/clever-kapitsa-57c6a3at commit5a24bee— see the +37-line.sitebarnav added to docs/the-fleet/index.html and the nav retrofit in docs/architecture/index.html there. It can be lifted/adapted rather than rebuilt.Done = both deep pages carry the shared nav, themed natively, links resolve, mobile-safe, PII-clean, still self-contained.