jiolab.dev redesigned itself three times today, and the third stuckjiolab.dev redesigned itself three times today, and the third stuck
August 22, 2026 · The site rebuilt its look three times in one afternoon, then made its project pages tell the truth about what's actually running, pinned, and next in line.The site changed its whole look three times in one afternoon, then fixed its project pages so they finally say what's actually running.
The site's own CSS got rewritten three separate times today, each pass replacing the last outright rather than layering on top of it. The first leaned agency-brochure: a bigger headline, a ruled numbered index in place of card grids. The second scrapped that for a palette lifted straight from the Frans Hals Museum's website, apricot against near-black teal, before a same-hour correction decided a museum's colors were wrong for what is, in its own words, “a log of things breaking at 3am,” and swapped in off-white and burgundy instead. The version that actually shipped, an hour after that, threw out the museum structure too: a hairline rail down the left edge, slash-prefixed monospace navigation, outlined headings, numbered listings instead of cards. All 231 pages re-rendered with each pass, so if you're reading this on the site, you're looking at attempt three.
The same day's other thread was an audit of what the projects page actually claims, and it turned out to be lying in both directions. Email-organizer's card said a feature was off when it was live and logging real activity. The vintage store map said one cell was filled in when two full sweeps had already run. Two projects, financial-manager and Reckreation, simply 404'd, because their pages had never been built. Both are published now, each with a new roadmap section describing what the project will actually do, with shipped items kept and grayed rather than deleted, so the page doesn't read as if nothing has happened yet. Projects can also be pinned now, overriding the homepage's “latest” card the way a blog post's pin does the opposite, because plain commit-recency could never have surfaced Reckreation, which had no commits at all until today.
The vintage map's own numbers moved because of a real fix, not just the audit. Its refresh job had its read budget capped at the same size as its discovery budget, so it found new stores exactly as fast as it could read old ones, and the backlog never actually shrank. Raising that budget took published stores from 30 this morning to 453, and district coverage from 13 of 35 to 28 of 35.
A ticket board that shows what's blocking what
Separately, the control plane's ticket board gained a second way to read it. /board/graph draws the same open tickets as bands, one per project, connected by their actual blocking relationships, which the flat list never showed. On today's board, 47 of 57 open tickets turned out to have a blocker. A follow-up pass added milestone lanes, so a chain of blockers climbing past its own deadline shows up as a schedule risk before it becomes a missed one. None of the day's 87 dependency edges ran backwards, but there's now a page that would catch it if one did.
The tunnel that puts this machine on the internet also went down for about seven minutes today. All four hostnames, jiolab.dev included, returned Cloudflare's own error page while the servers behind them stayed healthy the whole time. cloudflared had received a clean shutdown signal from somewhere unidentified, and its restart policy only covered a crash, not a clean exit, so it correctly stayed down until someone noticed. It's back up now and reconfigured to restart either way. What actually sent that signal is still unknown; the same thing happened once before, five days ago, with no cause found then either.
The site changed its look three times in one afternoon, and only the last one stuck. It started with a bigger, boxier header, tried on a museum's color scheme next, and ended up on a third look entirely: a thin line down the left edge, a small typewriter-style menu, off-white and dark red. Every page got rebuilt each time, so what you're reading this post in is the third attempt.
I also checked whether the projects page was telling the truth, and it wasn't, in both directions. One project's page said a feature was off when it was actually running. Another undersold two rounds of real work as barely started. Two projects didn't have pages at all. Those are all fixed now, and each project page lists what it's actually going to do next, keeping old goals visible instead of erasing them once they're done. I can also pin a project now, so the homepage shows what I'm actually working on instead of just whatever had the most recent commit. That mattered today, since my newest project hadn't had a single commit until today.
One of those pages, the map of vintage stores, had a real bug behind its numbers: it was allowed to read old listings at only the same speed it found new ones, so the pile of unread stores never actually shrank. Fixing that let it publish 453 stores today instead of 30, more than doubling how much of the city it actually covers.
Separately, the internal dashboard that tracks all my open work got a new view that draws tickets as a chain of what's blocking what, instead of a flat list, so it's obvious when a task is stuck behind something scheduled later than what it blocks. And the tunnel that connects this machine to the internet dropped for about seven minutes today, all on its own, for a reason nobody has found yet. The same unexplained drop happened once before, five days ago. It restarts itself properly now either way, crash or clean exit, but the actual cause is still a mystery.