Gutenberg Times: WordPress, AI, and the generational shift: insights from #WCUS Creators Studio

11 September, 2025 wkmph 0 Comments 1 category

Automattic’s Developer Advocates didn’t hold back at WordCamp US. Jonathan Bossenger, Brian Coords, Birgit Pauli-Haack, and Ryan Welcher sat down for a no-BS roundtable about WordPress’s future, AI’s actual role in the CMS world, and the big question: Is WordPress still cool enough for the next generation of developers?

This wasn’t your typical conference panel with rehearsed talking points. The conversation dug into how WordPress is evolving right now—messy bits, growing pains, and all.

Is WordPress headed for “Legacy” status?

The episode opened with a gut-punch question from a ChatGPT impersonation of a 25-year-old YouTuber: Is WordPress becoming a “legacy CMS,” or does it still belong at the cutting edge of web development?

The panelists weren’t having it. Birgit jumped straight into the modernization happening right now—Gutenberg’s evolution, sophisticated admin interfaces, and the shift toward block-based design systems. This isn’t your grandfather’s WordPress dashboard.

Brian kept things grounded: Sure, newer technologies like React and Vite deliver flashy front-end experiences, but guess what? Most projects eventually need a solid content management foundation. WordPress still delivers out-of-the-box content modeling, user authentication, and integrations that would take months to build from scratch elsewhere.

No-Code dreams or developer nightmares?

The conversation shifted to whether Full Site Editing and block themes actually simplify web building or just create new headaches for developers.

Jonathan pushed back on the “things are getting messier” narrative. His take? Structured, scalable paradigms always require an adjustment period. It’s not messier—it’s different, and that learning curve is normal.

Birgit shared a telling example: features like custom block styles that once required developer intervention are now accessible to content creators. It’s empowering non-developers while maintaining professional guardrails—exactly what good tooling should do.

Brian’s perspective? The block paradigm creates consistency. More people can build and customize using standardized approaches instead of fighting with fragmented solutions.

The subtext here: WordPress isn’t dumbing down. It’s getting smarter about who can participate in the building process.

Winning over the next generation

A big conversation centered on how WordPress stays relevant for younger developers swimming in a sea of shiny new options. Does WordPress still feel fresh? The team didn’t dodge the question.

It’s true: WordPress needs to meet new developers where they actually hang out—YouTube tutorials, TikTok quick hits, and mobile-first learning. Gone are the days when developers solely learned from documentation and forums.

Jonathan hit a key point: WordPress must keep demonstrating its power and possibilities, not just its legacy. Brian backed this up with market reality—there’s still solid demand for both PHP and React skills within the WordPress ecosystem. The work is there if developers want it.

But here’s the proof point that really landed: Birgit shared CERN’s story—yes, the global research powerhouse—migrating thousands of websites to WordPress. The kicker? Younger developers on their team were leading the charge.

That’s not a platform declining. That’s a platform adapting and attracting fresh talent where it matters most. The question isn’t whether WordPress can compete for the next generation—it’s whether we’re telling that story loud enough.

WordPress and Headless: the reality check

Panelists were clear: WordPress has the headless chops with REST API and GraphQL support, but that doesn’t mean everyone should jump on the bandwagon. Despite the industry buzz, most sites simply don’t need headless architecture.

The sweet spot? Clients with significant budgets or organizations treating WordPress as a content hub that feeds multiple touchpoints—other applications, mobile experiences, or external APIs. For everyone else, traditional WordPress delivers faster launch times and simpler maintenance.

What’s interesting is the innovation happening on both fronts. Developers are not only exposing WordPress data through REST and GraphQL but also pulling external data sources like Airtable directly into the block editor. That’s where the real magic happens for most teams.

In reality, headless setups are complex beasts with multiple failure points and hefty price tags. Traditional WordPress wins the speed-to-market race and keeps maintenance headaches to a minimum.

The infrastructure is solid, and real projects are shipping, but headless remains the exception rather than the rule. The ecosystem continues doubling down on improving core WordPress while keeping headless as a powerful option when the benefits justify the investment.

The short version: headless WordPress is a tool, not a mandate. Choose wisely based on your actual needs, not the hype.

AI integration—beyond the buzzword

You knew AI would come up—it’s practically mandatory at every tech event these days. But the panel cut through the noise with some practical reality.

Here’s the thing: AI-powered plugins have been around for a while now. The real challenge isn’t adding more AI features—it’s creating unified standards and APIs at the Core level. Think image generation, content creation, and debugging tools that actually work together instead of operating in silos.

Brian nailed the infrastructure angle: WordPress needs to pick standards that balance extensibility with privacy. Not everyone wants their content shipped off to massive cloud-based LLMs, and rightfully so.

The smart play isn’t chasing every AI trend that pops up on Product Hunt. It’s building the foundation that lets developers integrate AI thoughtfully—whether that’s keeping processing local, giving users control over their data, or ensuring different AI tools can actually talk to each other.

AI in WordPress isn’t about being flashy. It’s about being useful secure and giving users real choice in how they want to leverage these tools. That’s the kind of AI integration that actually moves the needle.

Will AI replace developers?

The panel didn’t dance around this one: AI makes developers more productive, not obsolete.

Jonathan kept it real about AI coding assistants like Copilot—they’re helpful, but they’re not magic. You still need actual developer expertise to review, modify, and debug what these tools spit out. Anyone who’s wrestled with AI-generated code knows it’s not exactly plug-and-play.

The bottom line? These tools change how we work, not whether we’re needed. Skilled, creative builders aren’t going anywhere.

The future: openness, community, and better storytelling

As the conversation wound down, the focus shifted to what really drives WordPress forward—community and storytelling.

Ryan made a solid point: WordPress professionals need to share more of their “hidden” case studies and innovations. We’re not just talking about what’s happening in plugin repositories, but the real work happening in agencies and institutions worldwide. Those stories matter.

Both Birgit and Jonathan pushed for more global showcases, bar camps, and informal spaces where grassroots innovation can surface. Because that’s where the real magic happens—not in conference keynotes, but in the trenches where people are solving actual problems.

The Conclusion

The panel’s take? WordPress is agile, dynamic, and very much alive. With ongoing improvements, strong community engagement, and thoughtful AI integration, the platform looks ready to keep powering the web for the next generation—and beyond.

Not bad for a 22-year-old platform that some people keep writing off.

Resources:

Category: Uncategorized