WordPress 7.0 “Armstrong” shipped eight days ago. If you’ve seen the breathless coverage doing the rounds, you’d be forgiven for thinking the future has arrived: real-time collaboration, AI integration, the whole package.
Reality is a bit messier. The headline feature got pulled at the eleventh hour. The release that was meant to be the official launch of Phase 3 — Collaboration — went out the door without the collaboration.
So let me give you the honest version, written by someone who’s about to roll this update across a bunch of client sites and has read more release notes than is probably healthy.
What WordPress 7.0 was supposed to be
Phase 3 of the Gutenberg project has been on the roadmap since 2018. The pitch was simple: Google Docs–style real-time editing inside WordPress. Multiple people in the same post at the same time, no more “this post is locked for editing by Steve” pop-ups, comments and cursors live in the editor.
This was the big one. Every WordPress agency, every content team that has ever fought over who’s editing the homepage, was waiting for this.
It didn’t ship.
Late in the release cycle, contributors found that the way the live-sync feature was saving data was quietly disabling WordPress’s query cache across the entire site whenever the block editor was open. The fix required building a new database table from scratch. The release got pushed six weeks. And then collaboration got cut from 7.0 entirely and bumped to a future release.
Translation: the cornerstone feature of the cornerstone release didn’t make it. That’s not a disaster — better to ship something that works than something that takes down your cache — but it means the “7.0 changes everything” coverage you’ve been seeing is missing the asterisk.
What did ship (and is actually worth knowing about)
A lot, to be fair. Here’s the version without the code snippets.
Native AI integration. This is the biggest real change. Up until now, if you wanted to use ChatGPT, Claude, or Gemini inside WordPress, you needed a separate plugin for each one, with API keys scattered everywhere. WordPress 7.0 adds a single Connectors screen under Settings. You enter your API keys once, and any AI-enabled plugin on your site can use them through a standardized interface. WordPress ships with built-in connectors for OpenAI, Anthropic, and Google.
There’s also an experimental plugin called AI Experiments that gives you AI-generated featured images, alt text, and excerpts out of the box. Genuinely useful for the right job. (More on the “right job” qualifier in a minute.)
A modernized admin. Buttons, menus, transitions — the whole dashboard has had a visual refresh to bring it in line with the block editor. Page-to-page navigation now uses smooth transitions instead of full reloads. Looks better, feels faster.
Visual revisions. Previously, comparing two versions of a post meant reading walls of text with red and green highlights. 7.0 shows revisions as a visual preview of the actual page, with changes highlighted at the block level. Spot a colour change, a moved image, a deleted heading — at a glance.
New blocks. A proper native Breadcrumbs block (no plugin required), a native Icon block with a built-in SVG library, and customizable mobile navigation overlays — meaning your mobile menu is no longer a fixed grey box, you can actually design it. The Paragraph block now supports text columns and first-line indents. Image blocks got aspect ratio and focal point controls.
Iframed editor. Technical change with a real-world payoff: the editor now loads in its own isolated frame, which means your theme’s CSS can’t accidentally break the editor UI, and vice versa. If you’ve ever had a site where the editor looks completely different from the front end, this is the fix.
The AI bit deserves a second look
I wrote a post last week about Google’s new AI search guide, and the headline of it was this: generic content is on borrowed time. AI can replicate it in 90 seconds. The only content that wins now is content only you could have written.
WordPress 7.0 just made it dramatically easier to generate generic content directly inside your editor. One click, AI-written excerpt. One click, AI-generated featured image. One click, AI-suggested categories and tags.
This isn’t bad. Used well, it’s a genuine time-saver — especially for the parts of content production that don’t benefit from a human voice. Alt text on a stock image. A tag suggestion. A first-draft excerpt you’ll edit anyway.
But the same rule applies. If you use the AI Connectors to spin up generic posts at scale, you’re racing toward the exact pile of commodity content that’s about to get summarized into oblivion. The tools got better. The bar didn’t move.
If you missed it, here’s my full breakdown of what Google actually said about AI content.
So… should you update right now?
Honest answer: no, not on a production site you care about.
Not because 7.0 is buggy — by all accounts it’s a solid release with extended RC testing. But major WordPress versions always shake out plugin and theme compatibility issues in the first few weeks, and you don’t want to find yours by having your homepage break on a Tuesday morning.
Here’s the rollout I’d actually recommend:
- Don’t auto-update. Turn off WordPress core auto-updates for major versions, if you haven’t already.
- Check your PHP version first. WordPress 7.0’s minimum is PHP 7.2, but 8.3+ is strongly recommended. If you’re on anything below 8.1, sort that out before you even think about 7.0.
- Stage it. Clone your site to a staging environment, run the update there, click through every key template, test your forms, test your checkout if you have one.
- Pay special attention to the editor. The iframed editor change can surface CSS issues that didn’t show up before. Walk through your most-used templates in the block editor and make sure nothing looks off.
- Check your plugins. Especially anything that adds custom blocks, custom admin UI, or hooks into the editor. Page builders, form plugins, anything Elementor-adjacent.
- Wait two weeks minimum. Let the early adopters find the bugs. Let plugin authors push their compatibility patches. Then update production.
If you’re a Holler hosting client, this is the bit I do for you — staged update, full regression test, scheduled deploy. It’s why “let me know when 7.0 is safe” is an email I’d rather you didn’t have to send.
The bigger picture
WordPress 7.0 didn’t deliver Phase 3. It delivered the foundation for it — and a genuinely useful set of changes alongside it.
The AI integration is the headline now. Native, standardized, multi-provider — that’s a real shift, and it’s going to change how plugin developers build for the platform over the next year. The dashboard refresh and visual revisions are quiet wins that make daily admin work less painful.
But if you were waiting for collaboration, you’re still waiting. And if you were waiting for “AI inside WordPress” to suddenly make content marketing easy — read last week’s post. It didn’t.
Want a hand thinking through your 7.0 update timeline — or just want this taken off your plate? Holler hosting clients get tested, staged updates handled for them. Book a 15-min Zoom → and I’ll walk you through what makes sense for your site.
