WordPress’s theme-for-design, plugin-for-functionality split was genuinely smart architecture. It protected users from losing everything when they wanted a fresh look. It created clear lanes for developers. It worked.

But “worked” is past tense, and here’s why.

The User Experience Gap

When someone opens the block inserter wanting a contact form, they don’t think “I need functionality, therefore I need a plugin.” They think “I want a contact form block.” The current model asks users to understand WordPress’s internal philosophy before they can build what they imagine.

This creates friction at every turn: leave the editor, search through thousands of plugins, evaluate quality and security, install, configure, return to the editor, find the new block. Meanwhile, platforms like Squarespace just have the block. It’s in the inserter. Done.

The separation optimizes for architectural purity over user flow.

The Coordination Cost

Every boundary creates a handoff. Theme developers can’t guarantee functionality. Plugin developers can’t guarantee their blocks will look right in your theme. When something breaks or looks off, users become detectives trying to figure out which piece failed. The clean separation on the development side becomes messy confusion on the user side.

Why AI Changes Everything

Here’s where it gets interesting. We’re entering a world where AI can generate blocks and functionality on demand. The old model assumed scarcity—you needed developers to build things, so separation helped them work independently.

But in a world where a user can say “give me a testimonials block that matches my site” and AI just… makes it? The boundaries become arbitrary barriers rather than helpful structure.

AI doesn’t care about theme versus plugin. It cares about solving the user’s problem. WordPress’s architecture should evolve to match.

A Path Forward

What if themes could ship with their own blocks—styled, integrated, ready to use in the inserter from day one? A theme’s testimonials block, contact form, pricing table, all right there when you need them.

The portability concern? AI solves that too. Switching themes could trigger an intelligent migration that rebuilds blocks to match new designs rather than breaking them.

The goal isn’t to tear down the separation entirely—it’s to stop exposing that separation to users who just want to open the inserter and find what they need. Let the architecture serve the people, not the other way around.

WordPress democratized publishing. The next step is democratizing the experience of building.