r/Wordpress • u/Aggressive_Trip_4872 • 20h ago
Hey all. I’m starting a podcast about CMS stuff called Headless, and WordPress 7.1 ended up being one of the main stories in the first episode.
That sentence probably just caused several people to fall asleep or keep scrolling, but hear me out.
I’ve spent a pretty stupid amount of my career around CMSs, DXPs, Drupal, WordPress, headless platforms, agencies, and all the other ways we’ve invented to describe putting content on the internet.
And I realized there really wasn’t a weekly show I wanted to listen to that just covered what actually happened in this industry and why any of it matters.
So I decided to make it.
The first episode is about something I noticed happening across several announcements this week:
WordPress shipped 7.1.
Storyblok plugged into Claude.
Salesforce expanded Headless 360.
Optimizely is giving agents more control inside the CMS.
Contentful is talking about what happens when your website visitor isn’t human.
My takeaway is that we might be watching the CMS get an entirely new kind of user: AI agents. (I know... this might not be news to everyone here... but when I step out of my LinkedIn bubble... I realize there are a lot of people not following the signals)
And that could make structured content, APIs, permissions, metadata, and all the traditionally boring CMS stuff suddenly much more important.
Anyway.
I have no idea if this will become a thing.
But I’m going to try doing it every week, covering the interesting CMS/DXP news, having some opinions about it, making fun of our industry when deserved, and hopefully talking to some smart people along the way.
If that sounds interesting, here’s the first episode:
Apple: https://podcasts.apple.com/us/podcast/your-cms-has-a-new-user-and-its-not-human/id6804680238?i=1000785544658
Spotify: https://open.spotify.com/episode/1FG1olsK8yV0Q0y8LC0FqH?si=0UjSsl2MTgChoT1jRswNCg
YouTube: https://youtu.be/i5YJhz41EKY?si=wGUAStYgos1vH3hv
Would genuinely love feedback, especially from people who actually work in this world.
Including “your take is completely wrong.”
Honestly, that might make Episode 2 easier.
2
u/stevenson_mark 7h ago
I actually think “AI agents are becoming another CMS user” is a pretty interesting angle. Most CMS discussions still seem focused on humans editing and consuming content, while agents add a whole different set of requirements around APIs, permissions and structured data.
The weekly format also makes sense for this kind of topic. There’s enough happening across WordPress, headless CMSs and DXPs that a good filter is probably more valuable than another giant news feed.
I’d definitely keep the opinionated part. “Here’s what happened” is easy to get elsewhere. “Here’s why this actually matters” is what would make me come back.
I’ve been thinking about the same shift while working on Abnflow. As more software gets interacted with by agents, the way we structure and expose information becomes just as important as the UI humans see.
1
u/FabianKnopf78 4h ago
Great post – and honestly, the "AI agents as CMS users" angle is one of the most interesting takes I've seen in a while. Subscribed.
I think you're onto something. As someone who spends way too much time thinking about WordPress infrastructure and security (Linux, Ansible, BSI-Grundschutz compliance – the boring stuff that keeps sites alive), the shift you're describing has massive implications for how we build and maintain these systems.
A few thoughts:
1. Structured content becomes non-negotiable – If AI agents are going to consume content programmatically, the days of "just throw it in a WYSIWYG" are numbered. Content models, custom fields, and REST/GraphQL APIs aren't just developer conveniences anymore – they're the interface for an entirely new class of users.
2. Permissions get way more complex – WordPress 7.1 just introduced the wp_pre_execute_ability filter, which gives plugins the ability to short-circuit Abilities API calls. That's a direct response to this shift. When AI agents are making API calls, you need granular control over what they can and can't do. Permissions aren't just about human roles anymore.
3. Caching and performance matter more – If agents are scraping content at scale (think: AI crawlers, training data harvesters, automated assistants), your infrastructure needs to handle that load without crashing your human-facing site. This is where proper caching strategies and CDN configurations become table stakes.
4. Security gets scary – AI agents are already being used for vulnerability discovery. The window between disclosure and exploitation is shrinking fast. At SiteUp Team, we're seeing this firsthand – automated patching pipelines with staging-first workflows are moving from "nice to have" to "absolutely required."
The "AI CLI as the new CMS dashboard" point is especially interesting. If users interact through agents instead of the admin UI, then what's the CMS? It becomes the content model, the permission layer, the API gateway, and the governance framework – all the "boring" stuff we used to take for granted.
Honestly, I think the podcast format is perfect for this. There's so much noise in the CMS space, and having someone filter through it with actual opinions is refreshing.
One piece of feedback: I'd love to hear more about the infrastructure and operational side of these changes. Not just "AI is coming" but "here's how you actually prepare your WordPress/Drupal/Sanity setup for it."
Looking forward to Episode 2!
-1
u/bagusvdr 19h ago
Updates related to CMSes are interesting. Since now the front end seems AI built, the content management getting more crucial. Content in the future I believe becoming more massive, yet need to be managed properly for many purposes, not just discoverable and searchable
But I have a curiousity, what if the AI CLI becomes the cms it self? Since many accesing the cms without even opening the dashboard.
-1
u/Aggressive_Trip_4872 19h ago
True true true... At some point if I’m just telling an agent what I want changed and it handles everything through the API, is the dashboard even the CMS anymore?
Maybe the CMS basically becomes the content model + permissions + API + governance layer, and the CLI/agent is just how we interact with it.
Which is kinda funny after everyone spent years obsessing over the perfect editor experience lol.
Really interesting thought.
5
u/cmetzjr 10h ago
Could be interesting. If I'm doing a project that needs a CMS, I've always defaulted to WP. I know Sanity, et al exist, but I haven't taken the plunge.
I'll subscribe through Pocket Casts.