pages (parent — the site’s route folder)

Purpose

src/pages/ is the Astro route folder: a flat directory whose .astro files map one-to-one to site routes (the only sub-directory is download/, a single dynamic route). It holds 22 route source files — the four 4–5k-line “giant” pages each get their own node, the remaining smaller pages are bucketed into four topical groups — across 8 documented children. This node is a pure parent: it has no direct content of its own (every line lives in a child file), so its value is the aggregate overview — what the route set is, how it splits, and what the pages collectively depend on. Per-file detail lives in the linked child DOCS and is not duplicated here.

The split is giants vs. groups: four single-file giant pages (index, phoenix-be, iris-reading, campaign) that each exceed a one-run read budget, plus four grouped nodes (_official-scam, _info, _commerce, _utility) covering the 18 smaller pages. DOCS placement follows the flat-folder convention (docs/_areas.md): single-file nodes → src/pages/<name>.DOCS.md; groups → src/pages/_<group>.DOCS.md.

Count note (correction): the prior docs (docs/_areas.md, the brief) say 21 route files; the actual count at 0abd819 is 22 .astro files (4 giants + 2 official-scam + 5 info + 5 commerce + 6 utility). The enumerations in _areas.md already list all 22 — only the summary number “21” is off by one. Carried forward as a surprise.

Children

The 8 page nodes below. Each hook is lifted from the child’s Purpose; see the linked DOCS for the per-file read (frontmatter, components used, dead imports, in-file data models). Routes are derived; this node duplicates no child content.

Giant single-file pages (4)

Grouped page nodes (4)

Dependencies

What the route set collectively relies on (rolled up from the child DOCS — each records its own exact imports):

Invariants / gotchas

Open questions