Latest / Wpfavs - Your favourite WordPress news / Open Weights, Lean Builders, and the New WP Stack

Transcript

Open Weights, Lean Builders, and the New WP Stack · Wpfavs - Your favourite WordPress news

• 0:13
  So WordPress officially signed onto the Open Weights and American AI Leadership open
• 0:18
  letter.
• 0:18
  And and look, at first glance you might think, okay, why is a content management
• 0:23
  system taking a political stance on open source AI governance?
• 0:28
  But it actually makes complete sense when you look at where site infrastructure is
• 0:31
  heading.
• 0:32
  Wait, explain that to me, because on paper it sounds like classic corporate
• 0:36
  advocacy.
• 0:37
  Why do web builders care if AI weights are open or proprietary?
• 0:41
  Because if proprietary AI models become the default gatekeepers inside your CMS,
• 0:46
  you are basically locking your entire workflow into closed third party servers.
• 0:52
  Open weights mean developers can actually run local agents,
• 0:55
  execute PHP safely, query databases directly on their own hosting without handing
• 1:01
  over total control to a single vendor.
• 1:03
  It is about keeping open source open at the foundational level.
• 1:07
  And you can see the friction happening right now in real time.
• 1:10
  I mean, look at Elementor laying off one hundred people recently.
• 1:15
  At the exact same time, you have this massive surge of targeted,
• 1:19
  lean AI extensions like Beaver Builder AI or the WP Editorial Workflow Generator
• 1:24
  blowing up.
• 1:25
  The monolithic, heavy visual builders are hit hard, while hyper specific micro
• 1:29
  workflows are taking over.
• 1:31
  Wait, so the era of the massive do it all page builder plugin is actually ending?
• 1:35
  It really feels like it, um, at least for people who actually build sites for a
• 1:40
  living.
• 1:41
  For years we crammed forty different features into one giant builder,
• 1:44
  and now site owners are dealing with massive code bloat and terrifying plugin
• 1:48
  abandonment stats.
• 1:50
  People are tired of paying for a heavy bloatware suite when all they want is clear
• 1:54
  performance.
• 1:55
  They want single purpose tools, things like StatsWP or Plugin Tracker that just do
• 2:00
  one job extremely well with zero friction.
• 2:03
  Right, because when an AI assistant like Claude or ChatGPT looks at a website,
• 2:07
  it does not care about your fancy drag and drop visual builder wrapper.
• 2:11
  In fact, all those nested divs and bloated JavaScript layers just make it harder for
• 2:16
  AI tools to parse what your site is actually saying.
• 2:19
  So the visual builder actually hurts how an AI sees and interprets the site?
• 2:23
  Totally!
• 2:24
  An AI content reader strips away the styling, strips away the visual fluff,
• 2:28
  and just reads raw structure.
• 2:30
  If your page is buried under twelve layers of builder wrappers,
• 2:33
  the machine gets confused.
• 2:34
  Lean code wins every single time.
• 2:37
  Which brings us right to the new Form Plugins Market Share twenty twenty six report.
• 2:42
  The legacy form tools still hold huge market share numbers,
• 2:46
  but the growth curves are flattening completely unless they offer deep,
• 2:50
  native AI agent compatibility.
• 2:53
  Having thirty field types in a form builder is not a selling point anymore if an AI
• 2:58
  agent cannot read or submit the payload cleanly.
• 3:01
  Is that why community sentiment around nominations for The WP Awards twenty twenty
• 3:06
  six feels so different this year?
• 3:07
  Oh, absolutely.
• 3:09
  The voting criteria have completely pivoted.
• 3:11
  Nobody is nominating plugins just because they have a flashy feature list or a
• 3:15
  million downloads from five years ago.
• 3:18
  People are voting based on rapid patch delivery, active maintenance reliability,
• 3:23
  and clean API architecture.
• 3:25
  In fact, if you look at the recent ecosystem reports, some of the most downloaded
• 3:29
  plugins in the directory have been unmaintained for three years.
• 3:33
  Users are finally waking up to that risk.
• 3:36
  Which leads straight into my big prediction for where this is all going next week
• 3:40
  and beyond.
• 3:41
  We are about to see search engines and AI discovery assistants start prioritizing
• 3:45
  site tools based on structured output readiness rather than raw repository download
• 3:50
  counts.
• 3:51
  Wait, break that down.
• 3:52
  AI assistants are going to ignore install counts?
• 3:55
  Think about it!
• 3:56
  If an AI assistant like Perplexity or Gemini is trying to recommend a product or
• 4:00
  pull data from a site, it does not care that a plugin has five hundred thousand
• 4:04
  legacy installs on WordPress org.
• 4:06
  It cares whether the site delivers structured, clean data through standardized APIs.
• 4:11
  Download count is a historical vanity metric; output readiness is actual current
• 4:16
  utility.
• 4:17
  I, I, I love that, because it rewards developers who focus on clean order,
• 4:22
  fast execution, and genuine usefulness rather than just riding social proof from ten
• 4:27
  years ago.
• 4:28
  So the big takeaway for site builders right now is simplify your stack,
• 4:33
  ditch the bloat, and prepare your data for machines, not just human eyes.
• 4:37
  Exactly.
• 4:38
  Make it easy for AI to read, and the rest takes care of itself.
• 4:41
  Alright, good chatting guys, talk soon.