• Great minds think alike? My WordPress take on Markdown for Agents

    Great minds think alike? My WordPress take on Markdown for Agents

    Today, Cloudflare announced Markdown for Agents, a feature that automatically converts HTML to markdown at the edge when AI agents request it. Reading their announcement felt like looking in a mirror. I’ve been building the exact same concept, even up to including frontmatter with metadata, independently, as a WordPress plugin called Markdown Alternate (which has…

  • The silence is deafening: Google’s “agentic” future leaves the WordPress economy behind

    The silence is deafening: Google’s “agentic” future leaves the WordPress economy behind

    Google just announced a massive shift in how the internet shops, and the biggest platform on the web wasn’t even in the room. If you haven’t seen it yet, Google recently dropped a bombshell announcement regarding the future of online retail. They are rolling out a new “Universal Commerce Protocol” (UCP) and a suite of…

  • The Tailwind paradox: the high price of “enough”

    The Tailwind paradox: the high price of “enough”

    The news hit the developer community like a cold bucket of water. Adam Wathan, the creator of Tailwind CSS, recently announced that he had to lay off 75% of his engineering team, cutting the staff from four engineers down to just one. The numbers he shared were staggering. Despite Tailwind being more popular than ever…

  • From installation to integration: Making plugins “agent-ready”

    From installation to integration: Making plugins “agent-ready”

    In my last post, I discussed why a design system is the “visual rail” AI needs. But the “Architect” I’ve been describing doesn’t just care about how a site looks; they care about how it functions. The problem today is that even the smartest AI is often a “clueless” collaborator. You ask a coding assistant…

  • Vibe coding is a trap: why WordPress needs a design system NOW

    Vibe coding is a trap: why WordPress needs a design system NOW

    In my last post, I argued that WordPress needs to become a “Base AI”: a structured foundation that AI can understand and build upon. Before that, I wrote about The Rise of the Architect, the person who will shift from writing code to orchestrating systems. But there is a massive obstacle standing in the way…

  • The generalization tax: why WordPress is still the smart architectural base

    The generalization tax: why WordPress is still the smart architectural base

    In my previous post, I discussed the demise of code copyright and mentioned what Dries referred to as the generalization tax. This had me thinking more about what that means for WordPress and investing in its ecosystem. For twenty years, the winning strategy in software was to build the “base layer”. WordPress won this race by becoming…

  • The death of Code Copyright (and the rise of the Architect)

    The death of Code Copyright (and the rise of the Architect)

    We are witnessing a strange paradox in software development. Thanks to AI code generation, more open source code is being created today than ever before. Yet, simultaneously, the value of a single line of code has never been lower. The commons (the vast library of open source projects that allowed AI models to learn how…

  • A new path forward for WordPress, and for the open web

    A new path forward for WordPress, and for the open web

    In December, I wrote about the state of leadership in the WordPress ecosystem. I shared how too much power rests with one person, and how the lack of transparent governance puts contributors and businesses alike in difficult positions. That post ended with a call: we need to lead. That wasn’t rhetorical. It was a pivot.…

  • Innovation in WordPress: a look at plugin development

    Innovation in WordPress: a look at plugin development

    Introduction  Recent observations have highlighted a significant surge in new plugin submissions to the WordPress repository, as noted in this post. We also know that Automattic recently “unpaused” their contributions, leading to some pretty critical articles like this one from Roger Montti. The increase in plugin submissions got Marieke and me wondering about the relationship…

  • The unintended consequences of making SEO “for everyone”

    The unintended consequences of making SEO “for everyone”

    At Yoast, we had one mission: make SEO easier. For a long time, SEO for everyone was Yoast’s tagline, and we meant it. We helped millions of people optimize their content. We made technical SEO more accessible. We gave small businesses, bloggers, and creators a real chance to be found online. And we were successful.…