Every post on this blog needs two images that do completely different jobs: a social card that has to earn a click in a feed, and an inline hero that opens the article. This post is about how the blog makes both — a typographic default that costs nothing, an opt-in artificial-intelligence (AI) cover that costs about four cents, and the little Model Context Protocol (MCP) server that wires an image model straight into Claude Code. The cover above was made by that exact pipeline.

You've seen this screen a thousand times: a dark page, the domain name in bold, "Performing security verification", and a lonely checkbox with the Cloudflare logo. It feels like a speed bump, but there's a surprisingly rich pipeline behind it — and, importantly, none of it runs on the website's own servers.

Software teams generate an ocean of numbers — commits, tickets, story points, lines of code — yet the thing we actually care about, performance, stubbornly resists measurement. This post is about that gap: why individual output is so easy to misjudge, what signals are worth watching, and how to measure teams without corrupting the very behavior you want.

"Self-maintaining" is a seductive phrase, so let's be honest about it up front. You're not going to walk away for a month and come back to a repo that grew new features on its own. What you can build is a loop where Claude does most of the mechanical work — turning issues into pull requests (PRs) — and a separate Claude pass reviews that work before it ever reaches you. You stay the final gate, but you review a clean, already-critiqued PR instead of a blank diff.

You add a <script> tag, the page runs your code. Underneath that one line the browser does a surprising amount of work: it decides when to run the script, fetches every file it depends on, figures out what each file is asking for, keeps every loaded module in memory so it runs exactly once, and evaluates them all in the right order. This is a tour of that machinery.

Every web developer knows the anxiety: a new framework trends on social media, a hot take declares your stack obsolete, and you wonder if you've fallen behind. The truth is that the web platform moves on a much slower, much more predictable clock than the discourse suggests — and the roadmap is public. You just have to know where it's published.

This post maps the sources that actually predict where the platform is going: standards bodies, browser vendor programs, runtime release schedules, ecosystem RFCs (request-for-comments proposals), surveys, and events. At the end there's a practical system for consuming all of it without burning out.

JavaScript had no built-in module system for most of its life, so the community invented one pattern after another to fill the gap. This is a chronological tour of how we got from global <script> tags to native ES Modules — and why each step happened.

Most of accessibility's real-world payoff comes from a handful of habits. This is the 20% of web accessibility work that delivers 80% of the results — the practices worth doing first.

Claude Code can be customized along a spectrum: at one end, plain-language instructions you hope the model follows; at the other, hooks and settings the harness enforces whether the model cooperates or not. This post maps that full surface and shows how to actually wire it up on a real project.

Marketing metrics answer the demand question: how do people find the product, what does it cost to bring them in, and are they worth more than they cost? SEO is the part of that question a frontend team is genuinely on the hook for — a chunk of it is frontend work — so it makes a natural bridge from performance metrics to growth ones. Here's the set, from the markup you own to the economics of a customer.