Open Weights, Lean Builders, and the New WP Stack

Nick d

So WordPress officially signed onto the Open Weights and American AI Leadership open letter. And and look, at first glance you might think, okay, why is a content management system taking a political stance on open source AI governance? But it actually makes complete sense when you look at where site infrastructure is heading.

Ido

Wait, explain that to me, because on paper it sounds like classic corporate advocacy. Why do web builders care if AI weights are open or proprietary?

Nick d

Because if proprietary AI models become the default gatekeepers inside your CMS, you are basically locking your entire workflow into closed third party servers. Open weights mean developers can actually run local agents, execute PHP safely, query databases directly on their own hosting without handing over total control to a single vendor. It is about keeping open source open at the foundational level.

Ben cohen

And you can see the friction happening right now in real time. I mean, look at Elementor laying off one hundred people recently. At the exact same time, you have this massive surge of targeted, lean AI extensions like Beaver Builder AI or the WP Editorial Workflow Generator blowing up. The monolithic, heavy visual builders are hit hard, while hyper specific micro workflows are taking over.

Ido

Wait, so the era of the massive do it all page builder plugin is actually ending?

Nick d

It really feels like it, um, at least for people who actually build sites for a living. For years we crammed forty different features into one giant builder, and now site owners are dealing with massive code bloat and terrifying plugin abandonment stats. People are tired of paying for a heavy bloatware suite when all they want is clear performance. They want single purpose tools, things like StatsWP or Plugin Tracker that just do one job extremely well with zero friction.

Ben cohen

Right, because when an AI assistant like Claude or ChatGPT looks at a website, it does not care about your fancy drag and drop visual builder wrapper. In fact, all those nested divs and bloated JavaScript layers just make it harder for AI tools to parse what your site is actually saying.

Ido

So the visual builder actually hurts how an AI sees and interprets the site?

Ben cohen

Totally! An AI content reader strips away the styling, strips away the visual fluff, and just reads raw structure. If your page is buried under twelve layers of builder wrappers, the machine gets confused. Lean code wins every single time.

Nick d

Which brings us right to the new Form Plugins Market Share twenty twenty six report. The legacy form tools still hold huge market share numbers, but the growth curves are flattening completely unless they offer deep, native AI agent compatibility. Having thirty field types in a form builder is not a selling point anymore if an AI agent cannot read or submit the payload cleanly.

Ido

Is that why community sentiment around nominations for The WP Awards twenty twenty six feels so different this year?

Nick d

Oh, absolutely. The voting criteria have completely pivoted. Nobody is nominating plugins just because they have a flashy feature list or a million downloads from five years ago. People are voting based on rapid patch delivery, active maintenance reliability, and clean API architecture. In fact, if you look at the recent ecosystem reports, some of the most downloaded plugins in the directory have been unmaintained for three years. Users are finally waking up to that risk.

Ben cohen

Which leads straight into my big prediction for where this is all going next week and beyond. We are about to see search engines and AI discovery assistants start prioritizing site tools based on structured output readiness rather than raw repository download counts.

Ido

Wait, break that down. AI assistants are going to ignore install counts?

Ben cohen

Think about it! If an AI assistant like Perplexity or Gemini is trying to recommend a product or pull data from a site, it does not care that a plugin has five hundred thousand legacy installs on WordPress org. It cares whether the site delivers structured, clean data through standardized APIs. Download count is a historical vanity metric; output readiness is actual current utility.

Nick d

I, I, I love that, because it rewards developers who focus on clean order, fast execution, and genuine usefulness rather than just riding social proof from ten years ago.

Ido

So the big takeaway for site builders right now is simplify your stack, ditch the bloat, and prepare your data for machines, not just human eyes.

Ben cohen

Exactly. Make it easy for AI to read, and the rest takes care of itself.

Nick d

Alright, good chatting guys, talk soon.