From a64ce34dfe01f6b0f8c534a3c6313eafc8eba7bf Mon Sep 17 00:00:00 2001 From: Oliver-Marcus Eder Date: Fri, 28 Aug 2026 20:02:11 +0200 Subject: [PATCH 1/7] =?UTF-8?q?docs(plan):=20Site=20Plan=20B=20=E2=80=94?= =?UTF-8?q?=20nav=20+=20homepage?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../plans/2026-08-28-siteB-nav-homepage.md | 715 ++++++++++++++++++ 1 file changed, 715 insertions(+) create mode 100644 docs/superpowers/plans/2026-08-28-siteB-nav-homepage.md diff --git a/docs/superpowers/plans/2026-08-28-siteB-nav-homepage.md b/docs/superpowers/plans/2026-08-28-siteB-nav-homepage.md new file mode 100644 index 0000000..47e89b8 --- /dev/null +++ b/docs/superpowers/plans/2026-08-28-siteB-nav-homepage.md @@ -0,0 +1,715 @@ +# Plan B — Navigation + Homepage Implementation Plan + +> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development to execute this plan. Work one task at a time, dispatch a subagent per task, and stop at each review checkpoint. Do not batch tasks. + +## Goal + +Ship the audience-first navigation and the non-technical story homepage of the +site redesign (Plan B of 4). Concretely: + +1. Rework the top nav to **Home · Learn · Use · Build** (+ GitHub), reusing the + existing data-driven `navItems` array and the existing mobile drawer. +2. Replace the current technical homepage (`site/src/pages/index.astro`) with a + **non-technical, no-diagram story scroll** in this exact order: + (1) The problem → (2) What OCF is → (3) Multi-sport (deliberately before + structure) → (4) Rough structure → (5) Where next (Learn/Use/Build). +3. Add three **area landing hubs** — `learn/index.astro`, `use/index.astro`, + `build/index.astro` — that link to the **existing** pages at their current + URLs (no page moving/merging happens here; that is Plan C/D). +4. Extend the CI accessibility route list to cover `/learn/`, `/use/`, `/build/`. + +Plan B is additive: existing pages (`docs/spec`, `docs/schema`, `docs/rulesets`, +`docs/features`, `examples`, `errors`, `ecosystem`, `playground`, +`playground/renderer`) stay exactly where they are and keep their URLs. + +## Architecture + +**Verified facts (2026-08-28):** + +- `site/src/components/Nav.astro` is **data-driven**: a `navItems` array in the + frontmatter is mapped into both the inline nav and the mobile drawer. Only the + array changes; the drawer markup, CSS, and focus-trap `