site
site/context-v/
15 files here
plans/3
Content Areas Index: Nested Filters, Word Counts, and Shared Cards
Rebuild /content-areas from parts the site already has, generalizing them along the way: two-level folder tabs, live word totals, and the reference and tool cards.
Upgrade All Dependencies for Faster Builds
Astro 6.1 → 7.3 and everything around it, in risk order. Speed is the motive, so measure it, because this site's Markdown setup may limit the gain.
site/plans
reminders/2
explorations/3
Abandoned Intention — The Tube Visual (four-layer branded container)
A retired attempt at a signature 'tube box' framing device — four concentric layered borders wrapping content — explored across three rendering strategies (CSS clip-path, raw SVG, Webkit) and never adopted. Captured here so the design intent survives the code being dropped in the site-next rebuild.
Rethink on Client-Focused Landing Pages
Three overlapping mechanisms — `for_clients` frontmatter, MOC files, and the `client-content/` tree — are trying to do the same job and stepping on each other. This is a thinking-out-loud document, not a spec.
site/explorations
issues/1
handoffs/2
Handoff — site → site-next rebuild kickoff (Phase 0 in progress)
Everything the next agent-session needs to resume the ground-up rebuild cold: the locked decisions, what was installed, what Phase-0 artifacts exist, what remains, and the exact next actions — including the gotchas (graphify under-captures .astro imports; the MCP query server becomes available in the NEXT session).
site/handoffs
decisions/3
Amend "Untouched": Allow a Scoped Dependency Refresh of the Current Site
The rebuild is paused and the build time hurts every content push. The current site can take dependency upgrades, provided its rendering stays the same.
Rebuild Keep/Drop Ledger — site → site-next (Astro 7 + astro-knots + LFM)
The Phase-0 ground truth for the ground-up rebuild: what the current site is made of, what survives into site-next/, what we retire — and the discipline that every retired thing gets its intention captured in context-v before its code is dropped.
site/decisions