Projects Dashboard

building · overview

This page is a short honest summary of what it is and the key decisions, not a full case study. Source status: private system: only a high-level description is safe to publish. Withheld: It renders the whole private workspace (every repo, fleet state, live status), so the code is inseparable from private data.

A single-file HTML dashboard over all my dev repos, with a drill-in for the AI-ops initiative tree. No build, no framework.

web

dashboard html personal

One HTML file, zero runtime dependencies, that reads across every repo in my dev folder and lays them out at a glance, plus a hash-routed drill-in for the AI-ops initiative tree. Deliberately boring and local-first: orthogonal to the operator-loop telemetry, this is just “what am I working on, everywhere, right now.”

Ship history

August 2026

A megabyte off every page open

Fifty-seven percent of the projects dashboard was a baked snapshot that every cold load downloaded and then overwrote with a live copy, for a view the page does not start on. It had been a month out of date the whole time, and being overwritten is why that never showed. The bake now writes the twenty highest-scoring entries and states on the page how many it left behind, the live fetch waits until that view is opened, and a cold load fell from 1.09 MB gzipped to 0.32 MB. A payload budget re-records itself downward whenever the page shrinks, and a refresher re-bakes the snapshots that had sat 24 and 33 days stale, refusing to run when the working tree holds changes it does not own.