The CTA that pointed at the wrong dev log

During a design review pass on the Deep Cut Atlas page, I caught something small enough that I’d walked past it for weeks. The only call to action on the page, “Follow along in the dev log,” linked straight to /blog. Not the project-filtered route. Just the whole blog, unfiltered.

The filtered route already existed. I’d built /blog/project/[project] a while back specifically so each product page could link to its own slice of the dev log instead of dumping visitors into everything I’ve written about Greenhouse or blog-manager’s syndication internals. src/data/projects.ts even already points its devlogHref at the right place for the homepage’s project cards.

But the one CTA that lives directly on the Deep Cut Atlas page never got the update. It was written before the filtered routes existed, and nothing forced it to catch up once they landed.

The fix is a one-line href swap in the page’s Astro file. The interesting part isn’t the fix, it’s how it survived. A page that’s presumably been looked at more than once, with a link that worked. No error, no 404, nothing a smoke test would flag. It just sent people to the wrong version of “the dev log” quietly enough that it took a design review, not a bug report, to notice.

Verified in a real browser: the CTA now lands on /blog/project/deep-cut-atlas, which already had matching posts waiting there.