Site Architecture Decision Record
Status
Accepted — single MkDocs build retained after navigation regrouping (Phase 2).
Context
The handbook contains ~117 pages spanning relationships, intimacy techniques, tutorials with external media, and India-focused reproductive health. Navigation was regrouped into clearer subsections without changing URLs.
Decision
Keep one MkDocs site at connection-handbook.pages.dev with:
- Thematic chapter tabs (01–11 after Family Journey split)
- Collapsed sidebar sections for heavy chapters
docs/family-journey/life-phase tree (Before → Pregnancy → Birth → First Year → Childhood 1–10) with graph-driven navigator- Bridge links from relationship curriculum pages to the family-journey hub
- Redirect maps for legacy
reproductive-health-india/**and root pregnancy paths
Alternatives considered
| Option | Pros | Cons |
|---|---|---|
| Single build (chosen) | One deploy, shared search, simpler redirects | Long nav tree |
| Separate reproductive-health build | Clinical audience separation | Dual deploy, cross-site redirects, duplicated theme config |
| Separate tutorials/media build | Isolates R2 media noise | Third deploy, fragmented search |
Revisit when
- Page count grows substantially beyond current scale and
- Collapsed navigation still fails usability spot checks and
- Audience analytics show persistent cross-contamination (clinical readers lost in intimacy nav)
Until then, bridge pages and chapter grouping are sufficient.
Shared assets
Theme, CSS, and JavaScript live under docs/assets/. Firebase analytics and Cloudflare Access assumptions are documented in the project README at the repository root (not published as a doc page).