This page is the gallery for the visual projects already in the library. It also shows whether each visual has the supporting docs needed to stay understandable and reusable over time.
Routes in the library
Every route is meant to feel like a reusable asset, not a one-off page.
Flagship project pages
The flagship pages carry the business-story visuals and the strongest communication structure.
Supporting docs linked
Route docs keep the intent, structure, and implementation notes recoverable for future edits.
Each card is a live route in the library, with a quick read on documentation health and how much supporting context it has.
4 project pages · 2 live routes
A live page showing the visual tools now available in the repo — diagrams, charts, motion, and interactive system mapping.
This page still needs its standardized support docs.
Open
Shows the old manual condo board request flow against the new logged system, with a connected architecture view and explicit operating costs.
README · docs/visuals/condo-board-communication-system/README.md
Context and intent · docs/visuals/condo-board-communication-system/context-and-intent.md
Data spec · docs/visuals/condo-board-communication-system/data-spec.md
Open
Shows the tech ecosystem, setup and ongoing cost categories, and where buying a service beats DIY.
README · docs/visuals/marven-baseball-sim/README.md
Context and intent · docs/visuals/marven-baseball-sim/context-and-intent.md
Data spec · docs/visuals/marven-baseball-sim/data-spec.md
Open
A Directus-backed visual timeline of projects with start/end dates and hoverable feature markers.
This page still needs its standardized support docs.
Open
Documentation
Each visual project should follow the same durable doc pattern so future work starts from context instead of guesswork.
One-page overview of what the project or visual is, what route it lives at, and why it exists.
What problem the visual solves, what the page should communicate, and what should remain true after redesigns.
The core content model, labels, metrics, relationships, or source assumptions behind the visual.
What was built, what is awkward, and what future contributors should know before editing it.