November 20, 2026
Not leaving WordPress

Within nine days, three well-known WordPress teachers on YouTube posted a video about where they stand. None of them is leaving WordPress, they say. Yet all three are clearly moving on. I watched (and transcribed) all three, and they have a lot more in common than the timing.

Three videos, one week

On November 11, Rino de Boer sat down with Jamie Marsland of Automattic, under the title: Why AI can’t ‘kill’ WordPress, it’s the opposite. I wrote about that one last week. On November 17, Jeffrey of Lytbox, who built his channel and community on Elementor tutorials, posted: Goodbye Elementor. And on November 19, Paul of WPTuts posted: I Need to Talk To You About the Future of WPTuts.

Three different people, three different stories. Jeffrey is angry with Elementor, Paul is calming his audience down and Rino is (again) asking out loud whether WordPress still makes sense. But listen closely and you hear the same five things.

1. The page builder is the part that is going

Rino quit Elementor last month. Jeffrey says goodbye to it now and moves to Bricks. Paul still covers Bricks, but what excites him is its MCP connection, so an AI can build the design. Gutenberg and full site editing? “I don’t really care about them.”

Rino explains why, in words Jamie gave him back in March: AI replaces the front-end layer, and that is exactly the layer the page builder owns. Not the database, not the CMS. The page builder is “the thing that is most sensitive to disruption”. Rino himself has not touched one in months: he builds his sites by prompting Claude inside WordPress.

Jeffrey adds a reason that has nothing to do with AI. Elementor V4 was supposed to be the professional, class-based workflow. Instead it was pushed onto live websites as a beta and then made compatible with V1, V2 and V3, mixing two builders into one. “They should have created V4 as a standalone.” Backwards compatibility, once again, holding the new thing back. Same thing Rino said earlier in another post.

2. WordPress is just the thing underneath

Not one of them talks about WordPress with any love. Paul says it plainly: “WordPress doesn’t really excite me anymore.“It is a means to an end”, “just the tool that all those things sit on”. Rino, after half a year of exploring other platforms, comes back to it for the same reason: it is “just a database with a CMS”, for free. Even Jamie, who works for Automattic, admits the site editor is “a system for building themes, not a system for building websites”.

That is a remarkable shift. WordPress used to be the thing these people taught. Now it is the plumbing, and the interesting stuff happens on top of it: Bricks, MCP, Claude, Rino’s own Pencil plugin.

3. Nobody knows what is relevant in six months

This is the one that hit me most, because it is a teacher’s problem. Paul: “a lot of things that I’ve covered in the past, we don’t know if they’re going to be relevant in 6 months time.” Jeffrey: “in 6 months or a year from now, things are going to be drastically more different.” Rino needed eight months to understand what Jamie told him in March.

A tutorial used to last for years. Now it might not last until spring. If your business is teaching a tool, that is scary. Jeffrey is honest about it: he felt stuck, lost, and took time off to figure out where to go.

4. They all ask the boring questions

All three distance themselves from the AI hype, and they do it in the same way: by asking about the parts nobody shows. Jeffrey: “we see the prompt […] but we don’t see, okay, how does the contact form work? How are you setting up security? How are you dealing with search?” Rino asks his clients whether they set up an email server, and whether their leads actually arrive. Paul warns that the $20 AI plans might not stay $20.

And Paul says the most interesting thing of all, almost in passing. He has moved some of his own websites away from WordPress “to remove the amount of maintenance and ongoing upkeep”. He now looks at Astro and tools that migrate WordPress sites with AI, for clients who do not need WordPress “but you don’t want them to end up paying for it”.

5. They fall back on people

When the tool is no longer the anchor, something else has to be. For Jeffrey it is his community: “community always comes number one”, and he ends his video with “you are not alone”. Paul points to his community of nearly 2,000 members. Rino tells his audience to stop selling “websites as sandwiches” and to sell results instead: more leads, more revenue, not pages.

That is the same move, three times. The value is no longer in a specific tool. It is in the people and in the result.

What they do not say

So what do they have in common? Three WordPress teachers, in one week, each saying “I am not leaving” while explaining why they no longer believe in the part they used to teach. They keep the brand, the community and the audience, which all live on WordPress. That is understandable. It is their livelihood.

But Paul accidentally named the elephant in the room I wrote about last week: maintenance. If AI builds the front end, and the CMS is “just a database”, then what is left of WordPress is the part nobody wants: the updates, the plugins, the security and the blame when it breaks. That is exactly why I build websites by hand, with the content in a separate CMS, and never update WordPress again.

They are not leaving WordPress. They are leaving the page builder, the tutorials and the excitement. What stays behind is the hosting and the updating. I wonder how long that will keep them.

()  Joost van der Schee