From the Nerd News Archive: our road retold in the voice of the moment. A story written today.
This archive started in a page builder, with a plugin for everything and a founder who did not know what he did not know. Seventeen chapters later, here we are. This is the closer, so let me put the whole road in one place.
The short version: WordPress, then Webflow, then fully custom code, with AI arriving late and rewriting what the last stretch cost. The long version is every chapter behind this one. But a road looks different from the end than it did from the middle, so here is what each stretch actually taught.
WordPress taught maintenance humility
I went in believing the job was building websites. WordPress taught me the job was keeping websites alive. Updates that broke things, plugins that fought each other, the backup you discover you needed right after you needed it. Divi and the plugin stack got me live, got clients live, and I am not ungrateful. But the lasting lesson was humility: every dependency is a promise someone else may or may not keep.
Yoast taught a separate lesson: search is a craft you can practice deliberately. The green lights were never rankings, but the habit of caring about titles, structure, and what a crawler actually sees started there and never left.
Webflow taught systems thinking
Webflow was the first tool that rewarded thinking in systems instead of pages. Classes instead of one-off styles. Symbols instead of copy-paste. Collections instead of a hundred hand-made pages. Native features quietly doing what a dozen plugins used to pretend to do. The plugin anxiety left, and in the silence it left behind, I could finally hear the design.
It also produced the framework I still use: template, wireframe, component library, or scratch, matched to goals and budget. Webflow made the middle tiers real, which made the whole framework honest.
Custom code returned ownership
Going fully custom was the move from renting to owning. No platform sitting between the work and the client. No monthly fee to keep your own pages on. The code is the site, the client owns the code, and nothing in the stack can raise its price or retire a feature out from under the business. In the old economics it cost more. It was worth it anyway.
AI changed the economics
Then AI-assisted engineering arrived, and the old economics stopped being the economics. The mechanical middle of a build got fast and cheap. The judgment around it became the whole job. Custom stopped being the luxury tier, and the durable assets turned out to be exactly the unglamorous ones: the quality bar, the checking, the taste, the refusal to fabricate. Those are the parts no tool supplies.
What each stretch left behind
- WordPress: humility about maintenance, and respect for search as a craft.
- Webflow: systems thinking, and a framework for matching the build to the budget.
- Custom code: ownership, and a quality bar with no platform left to blame.
- AI: speed, with no discount on judgment. The bar stayed human.
The chapter being written now
The current chapter does not live in this archive. It lives in the rest of Nerd News, in the present-day posts about what the studio builds, checks, and refuses to fake right now. This archive ends where those begin. If you want to know how the story goes from here, it goes there, one post at a time.
Why this archive sounds the way it does
One last thing, about the shape of what you just read. Every chapter in this archive speaks in the voice of its own moment. The WordPress chapters do not know Webflow is coming. The Webflow chapters do not know about custom code. The early chapters have never heard of a machine writing anything. That is a storytelling choice, made in the open: all of it was written now, it says so, and the metadata carries today's date because that is the truth.
I wrote it this way because hindsight flattens everything. From the end, each stretch looks like an obvious step toward here. From inside the moment, none of it was obvious: the plugin stack felt permanent, Webflow felt like the end of history, and walking away from both felt like a risk. Present tense keeps the uncertainty, and the uncertainty is where the learning lived.
That is the road. Thanks for walking it with me. The next chapter is the one being written now, and for the first time on this road, I get to write things down while they happen.
