spec - nav.test.ts

Referenced by3

Labels3

Idea	Status	Tags	Summary	Katz
elevator_pitch_section	done		Landing `#elevator-pitch` after [hero_section] and before [featured_in_section]. This is the home " Why reqlan " destination: [sidebar_nav] child and [nav_graph] Why node use this id. One-line thesis plus rotating claims. Copy lives in ["../../site/src/content/meta.ts"] per [copy]. Thesis follows ["../constitution.rq".elevator_pitch]. Behaviours: [claim_cycle], [claim_progress], [claim_reduced_motion], [claim_expand]. Styling per [styling_architecture]. Must stay compatible with [simple_lightweight_and_static].	0.123
nav_graph	done		Sticky landing page graph. Node / edge model and labels live in ["../../site/src/content/nav.ts"] per [copy] / [sidebar_nav]. Section nodes match home anchors; page nodes match top-level routes in [routes].	0.123
sidebar_nav	done		The site sidebar is a hierarchical page nav, not a flat list of mixed anchors and routes. Top-level entries are pages ( or the home hub ). Same-page section anchors nest as children under their parent page. Children render only while the visitor is on that parent page — off-page section lists stay collapsed so the sidebar reflects the current route. Until pathname is known after mount, children stay closed ( do not default to Home ) so static HTML / hydration does not flash a mismatched hierarchy. The active page uses `aria-current="page"`; the in-view same-page section uses `aria-current="location"` when known. Nav model and labels live in ["../../site/src/content/nav.ts"] per [copy]; the Sidebar client reads pathname ( and hash / section when on home ) to decide expansion and current markers. FAQ is a top-level page entry per [faq_page]. Support is a top-level page entry per [support_page_reqs.support_page]. Sidebar nests Support section anchors as same-page children.	0.187

Reference labels

elevator_pitch_section, nav_graph, sidebar_nav