Dropping the Spotify link
I pulled the Spotify link out of this site’s Music section this week. Not a UI change, a decision - I’m boycotting Spotify going forward, and that meant looking at everywhere the site pointed people there.
The catalog itself is staying up. Vicstradamus has been on Spotify for years, long before I decided to stop pointing new traffic at it, and pulling existing releases down felt like punishing past-me for a call I’m making now. So: no new links to Spotify anywhere on the site, but the grandfathered catalog stays put. That’s the line I drew.
The fix was one line - src/data/projects.ts has a music.links array feeding the Music section’s link grid, and Spotify was just one entry in it. Delete the entry, the grid re-renders with one fewer tile, done. No component logic to touch since the grid maps over the array generically - no per-platform icon or styling keyed to “Spotify” anywhere.
The only interesting part was making sure it actually looked right afterward - four tiles instead of five in a two-column grid, no dangling reference to the platform in the footer or anywhere else in the codebase. Grepped for “spotify” case-insensitively across src/ and public/ after the edit and got nothing back.
Small change, but it’s the kind of thing where the code is the easy part. Sister change on the Vicstradamus site next.
Related reading
The filter pills existed, just not where anyone could find them
Per-project filtered views with a nice pill nav - reachable only from homepage cards. The main /blog index, where everyone actually lands, had no way in at all.
The CTA that pointed at the wrong dev log
The only call to action on the Deep Cut Atlas page linked to the whole unfiltered blog - a link that worked, returned 200, and quietly sent everyone to the wrong place for weeks.
The linter was pointing at the right line for the wrong reason
An attribute I nearly deleted on an assumption, an overflow that only exists at phone width, and an a11y suite that passed on every version of this - broken and fixed.