Over the past year, I’ve been developing a new approach to educational content for YouTube, X and LinkedIn in the age of AI.

The approach is pretty simple: build something exciting, show it working, then teach people exactly how I did it.

Less theory about what AI might make possible. More: here’s what I built, here’s the prompt, here’s where it broke, and here’s how you can try it yourself.

Recently I went back through the comments on my videos and posts to see what actually happened next.

There’s a surprisingly clear pattern.

Show something exciting first

On Is this the Future of WordPress?, the top comment came from Jochen Steckert:

“Please make a complete tutorial, Jamie.”

195 people liked his comment and 16 replied. So I made the tutorial.

On another video I demonstrated building a WordPress plugin without coding and asked whether people wanted the plugin. More than 30 people said yes. So I finished it and released it (for free).

Mark Bracking asked, “will you provide more instruction videos?” Carter Angon asked for an entire “How to Claude with WordPress” series based around practical use cases.

The recurring response wasn’t simply this is interesting.

It was show me how.

Then watch what people do

This is the bit I care about most.

Tyron Bache discovered WordPress Studio through one of my videos, built his first plugin and submitted it to the WordPress Plugin Directory.

Nasir Haidary shipped RTL Enhancements. Another viewer used a technique I’d demonstrated to clear more than 30 orphaned posts from their site.

Dejan Buric is perhaps my favourite example. He told me, “I don’t know much about coding,” then used Telex to create an enhanced Core Details block. It did almost everything he wanted, so he came back to ask about the one thing he couldn’t get working.

He’d gone from viewer to builder with a bug report.

That’s changed how I think about educational content

The pattern I keep seeing is:

That’s interesting → Show me how → I tried it → I built something → Here’s where I got stuck.

And that last step is particularly useful because it creates a feedback loop. People come back, ask better questions, suggest features and show me where the gaps are. One of my plugins reached version 0.3 directly because of feedback from someone who tried it.

So my approach to educational content is increasingly:

Build → Show → Teach → Listen → Build again.

In an age when AI makes it incredibly cheap to tell people what’s possible, perhaps the most useful educational content does the opposite.

Show something real. Then help someone else do it.

And maybe the best measure of whether it worked isn’t “Great video!”

It’s “I tried this…”

---

Appendix: The Receipts

Everything below is taken from the comments and evidence I reviewed. I’ve included the positive responses, evidence of people taking action, repeat participants, peer engagement, downstream activity and the pushback. The point isn’t to pretend everyone agrees. It’s to show what actually happened.

A. “Now teach me” — tutorial demand

Jochen Steckert — Is this the Future of WordPress?

“Please make a complete tutorial, Jamie”

195 likes and 16 replies. This was the top comment. I subsequently made the tutorial and pinned it.

30+ separate commenters — Build a WordPress Plugin Without Coding — Cursor AI

More than 30 people replied with some version of “Yes please” when I offered to release the plugin. The result was Play Video on Scroll, which I subsequently released for free.

Mark Bracking — WordPress.com Just Got Its Own AI Assistant

“Is there a document library for the AI assistant on what we can accomplish by using this feature, and will you provide more instruction videos?”

51 likes, making it the highest-voted comment across the WordPress.com AI videos in the analysis.

Carter Angon — It’s Official: You Can Now Use Claude with WordPress!

“Thanks Jamie! This is awesome! Could you guys bring a ‘How to Claude with WordPress’ series with the possible most practical and productive use cases? That would be FANTASTIC”

13 likes.

@spiggott and @websparkone — same video

Two separate comments, 16 likes each, both asking how to do it on self-hosted WordPress.

@ZeEN.Artist

“I like your courses Thank you so much we need more plz”

Daniele Manca

“Great tutorial, is there one which shows the build of a wordpress theme instead?”

8 likes.

@yusuf90s

“awesome content! please more”

@sarahd_runner — Telex AI Builds WordPress Blocks

“how do we check security of what we make? Could this be a future video?”

B. People who actually built or used something

Tyron Bache discovered WordPress Studio through the Cursor video, built his first plugin and submitted it to the WordPress Plugin Directory.

Nasir Haidary shipped RTL Enhancements.

@inn8ly cleared more than 30 orphaned posts using the Cowork technique demonstrated in the video.

Andy Rush — The New WordPress Editor Built for Writing

“I love it! Discovering its quirks and limitations now… but it’s miles ahead of using the classic block or distraction free mode to write. I’ve downloaded the plugin for one of my hosted sites.”

Dejan Buric — Telex AI Builds WordPress Blocks

“Thank you very much Jamie for this very useful video. I don’t know much about coding and I tried to have Telex create an enhanced Core Details block for me. It did everything I asked for perfectly, but there was one thing it couldn’t do…”

The remaining issue was Block Spacing.

@suziecycles — same video

“It’s amazing but also frustrating for beginners. I got a whole lot of ‘That didn’t work as expected, let me try a different approach.’ but no change in the results. Still, it’s a start.”

She was trying to build an Advent Calendar block.

@anythingapproacjing

“No way ive been using this system internally for over a year. Mine does deep research then send to an ai editor then sends to wp editor, then sends direct to wp backend.”

This was the top comment on that video, with 53 likes.

Bernard Guy — Claude connector video

“Nice. Started using it. Any idea about the timeline as to when the edit function will be rolled out?”

@grierson2020

“Thank you for the helpful guide in setting up MCP. I am really loving the ability to do this!”

@TheWPGuy built a working app in three prompts and packaged a Claude Skill based on the workflow.

The Front-End Editor for Content Teams v0.3 also shipped directly from feedback in a user’s review.

C. Bookmarking as an intent signal

On the design system → AI agent → WordPress site post on X, there were 229 bookmarks compared with 122 likes.

The front-end editor built with the Interactivity API + Claude Code in Studio received 93 bookmarks, alongside 141 likes.

The Wix → WordPress with ChatGPT post received 37 bookmarks.

The Fable 5 block theme test received 85 bookmarks.

The “Weekend challenge: Build ‘Canva for WordPress’” LinkedIn post generated 158 reactions, 27 comments and seven reposts.

A bookmark obviously doesn’t prove subsequent action, but it provides another useful signal of intent: people aren’t only reacting to the content, they’re saving it.

D. People saying the thesis back to me

@name_is_false — WordPress Studio + MCP

“The most interesting part here isn’t the AI itself, but the fact that it works through standard WordPress workflows and remains editable afterward.”

They went on to argue that keeping AI-generated changes close to normal WordPress tooling makes them easier to understand, maintain and build on.

@timmcreynolds2734 — Telex AI Builds WordPress Blocks

“Good Grief. How much fun is this? Loved the untouchable button. How do you have time to find all of this stuff? I appreciate your sharing that with us. This stuff just got fun.”

@glenyst5216 — writing editor

“This is brilliant. I have a few writer clients and they prefer something simpler.”

@SuziQ-fg4ee — writing editor

“This looks fantastic. I can’t wait to try it on my blog. I must admit I found the original block builder really tricky to use.”

Elliott Richmond engaged at the product level, suggesting the writing experience could ship under Options → View as “Writer Mode.”

@IhabQandil — Studio + MCP

“This was super helpful, thanks!”

@Thequirkfiles

“Nice. Been waiting for this.”

@jakirulislam5191

“So much helpful. Thanks for sharing.”

8 likes.

E. People who keep coming back

Aamir Farooq has commented on Telex AI Builds Blocks, WordPress.com Just Got Its Own AI Assistant and My New Favourite Way to Vibe Code WordPress, as well as replying on X.

On the Studio video he asked for every block to be draggable and positionable “like Canva.”

Other recurring participants across the discussions include Moe U., @stratosvlasakidis7319 and @PaalJoachimRomdahl.

F. Peer and industry engagement

Matt Mullenweg joined one discussion to point out that WordPress + AI success stories were happening through the REST API with an application password, WP-CLI or SSH.

Others who engaged in these threads included Katie Keith, Syed Balkhi, Dave Winer, Rich Tabor, Andy Peatling, Brian Coords, Anh Tran, Tyler Moore, Fellyph Rozendo Cintra, Carl Hancock, Nilo Vélez, Sean C Davis, martinibuster and RETipster.

@visualmodo commented:

“Very good video!”

G. Other creators exploring the same territory

After I published It’s Official: You Can Now Use Claude with WordPress!, other creators subsequently published their own WordPress + AI content.

Darrel Wilson published Build a WordPress Website with Claude in 2026, Easily Connect Claude AI to WordPress in 3 Minutes, and How to Connect Claude to WordPress — Just Copy & Paste!.

WPTuts published Is WordPress Dead? My Honest Take on AI vs WordPress.

Ryan Welcher has also explored Studio Code and WordPress blocks.

I can’t establish causation here, and don’t claim it. The interesting observation is simply that the category is now being explored independently by other WordPress educators.

H. The pushback

This matters too. Showing real things doesn’t only generate enthusiasm. It gives people something concrete to challenge.

@Black1991Star — Studio + MCP

“We don’t need it. This doesn’t look secure, you are giving a third party full access to your site.”

Interestingly, the same person left a positive, curious comment on the writing editor. The objection was specific rather than simply anti-AI.

@markjs and @pshemekm also raised concerns around application-password security.

@zackary_aiseo — Telex

“each AI-generated block is a plug-in. It’s terrible.”

@PsalmLab

“How is WordPress protecting the creator economy from IP infringement with Claud?”

@ChristoherGardner raised the gap between AI-generated HTML and a genuinely maintainable theme.

Rich Tabor flagged improper block output.

Alissa Condra raised perhaps the most fundamental question: if AI can generate the whole site, why WordPress at all?

@ShadowWingTronix — writing editor

“It looks like a rework of the Classic Editor to me… Right now I’m happy with Classic.”

@studytunes8549

“Great there goes my web agency in 1 year.”

@TheBeeOBee

“Would love to know why only men are into vibe coding. And have women explain it.”

@DeCowebdev left a strongly negative response without an accompanying argument.

There were also several threads around Cowork sandbox 403 / allowlist problems.

And @anthonyabroad_exe encountered a permissions issue requiring a Jetpack Complete or Jetpack AI plan on self-hosted WordPress.

The pattern

Taken together, the comments show a much richer progression than simple positive or negative engagement:

Show me how → I tried it → I built something → Here’s my problem → Here’s what I’d change → What are you making next?

That’s the loop I’m trying to optimise for.