I’ve been on WordPress since 2009. That’s 17 years of watching this platform evolve — through the TinyMCE era, through the chaos and controversy of the Gutenberg block editor launch, through every major version bump that either delighted or frustrated me. I’ve grown with it, complained about it, and kept coming back to it.
A few years ago, I even jumped ship — briefly. I migrated over to ClassicPress, a community-led fork of WordPress 4.9 that strips out Gutenberg entirely and keeps the classic editor front and center. It’s lightweight, stable, and for a certain type of builder — especially those who never warmed up to blocks — it genuinely makes sense. I understood the appeal. But ultimately, I found myself back on WordPress. The ecosystem, the community, the sheer momentum of the platform pulled me back. And honestly? I’m glad it did.
Because May 20, 2026 was a date worth circling for anyone who builds on WordPress. That’s when WordPress 7.0, codenamed “Armstrong,” officially launched. And while the headlines leading up to it were dominated by promises of real-time collaboration (more on that in a moment), what actually shipped is arguably more important: a foundational AI layer baked directly into the core of the world’s most popular CMS.
This isn’t a minor update. It’s the biggest structural shift WordPress has seen since the block editor arrived in 2018 — and it has real implications for how web designers work, build, and deliver results for clients.
Let’s break it all down.
A Little Context First
WordPress 7.0 opens Phase 3 of the Gutenberg project — the collaboration and workflow phase of the platform’s four-step development roadmap:
- Phase 1 (2018): The block editor replaced the classic editor
- Phase 2 (2021–2024): Full site editing gave designers block-based control over the entire site
- Phase 3 (2026+): Collaboration, workflows, and AI — starting now with 7.0
- Phase 4 (2027+): Core multilingual support
The release was actually delayed from its original April 9 date to give the team more time to stabilize features, and real-time collaboration was ultimately cut from this version. But what remained is no consolation prize. WordPress 7.0 lays infrastructure that will define the platform for years.
The Big One: WordPress Gets a Native AI Layer
The headline feature for web designers is the introduction of the WP AI Client and the Abilities API — a standardized AI infrastructure built directly into WordPress core.
Before 7.0, every AI-powered plugin had to build its own separate connection to providers like OpenAI, Google Gemini, or Anthropic Claude. Each one stored its own API keys, handled its own requests, and introduced its own potential vulnerabilities. If you used three AI plugins, you were managing three separate integrations, three sets of credentials, and three potential points of failure.
WordPress 7.0 replaces that fragmented approach with a single, shared AI layer. After updating, you’ll find a new Settings > Connectors screen in your wp-admin dashboard. It lists default AI providers — OpenAI (ChatGPT), Google Gemini, and Anthropic Claude — and you can connect others as well. Enter your API key once, and that connection is shared across every plugin that supports the new standard.
For web designers, this means:
- One AI setup, site-wide. No more juggling multiple plugin configurations.
- Consistent AI behavior across different tools and workflows.
- Better security through centralized credential management.
- Future-proofing as the plugin ecosystem builds on this shared infrastructure.
The Abilities API also gives site owners control over what AI tools are permitted to do. Plugins must explicitly register their capabilities — things like creating posts, editing metadata, or generating image descriptions — and they operate strictly within those defined boundaries. For designers building sites for clients, especially in regulated industries, this kind of permission architecture is a welcome addition.
The Admin Dashboard Gets Its First Real Facelift Since 2013
Web designers spend a lot of time in wp-admin. WordPress 7.0 finally gives it some love with the introduction of DataViews — a new React-based interface for managing posts, pages, media, and users.
Gone are the classic PHP-rendered admin list tables. DataViews is faster, more modern, and visually cleaner. Think of it as the admin experience finally catching up with the block editor’s aesthetic.
The update also includes visual refresh elements across the dashboard — refined typography, improved spacing, and UI adjustments that make the admin area more comfortable during long work sessions.
Visual Revisions Replace Real-Time Collaboration (For Now)
The most hyped feature for WordPress 7.0 was real-time collaboration — the ability for multiple users to edit the same page simultaneously, Google Docs-style. That feature was officially removed from the release on May 8, 2026, and isn’t expected to arrive until at least 2027.
What shipped instead is Visual Revisions — a significant upgrade to how WordPress tracks content changes. Rather than digging through code strings in a compressed revision history, designers and editors can now track changes visually across the editor interface. Spotting what changed, when, and where becomes a visual exercise rather than a code-reading task.
It’s not real-time collaboration, but it’s a genuinely useful improvement for teams managing content on client sites.
Design Tools: Font Library and Responsive Controls
WordPress 7.0 brings an updated Font Library window inside the Appearance menu. Custom typographical assets now load and preview without any code interaction required — the window integrates cleanly into the existing workflow rather than opening as a separate tool.
The release also introduces improved responsive visibility controls, making it easier to show or hide blocks across different screen sizes — a quality-of-life win for designers building mobile-first experiences.
For Developers: PHP-Only Block Development and Staging Improvements
On the developer side, WordPress 7.0 introduces PHP-only block development — a simpler path to building blocks without requiring a full JavaScript build toolchain. For designers who are comfortable with PHP but less so with Node.js-heavy workflows, this is a meaningful accessibility improvement.
The release also includes improved staging workflows and WordPress Playground integration, making it easier to test changes before pushing to production. A safer, faster iteration cycle is something every web designer can appreciate.
What About Compatibility?
WordPress 7.0 requires a minimum of PHP 7.4, though the core team strongly recommends PHP 8.3 or higher for optimal performance and compatibility. Full support for PHP 7.2 and 7.3 has been dropped.
In most cases, sites running WordPress 6.x should continue working fine after the update — backward compatibility remains a core WordPress principle. That said, always back up before upgrading, and test heavily in a staging environment if your site runs older plugins or customized checkout flows.
The Bottom Line for Web Designers
WordPress 7.0 is not the flashy collaboration release it was marketed as. Real-time editing didn’t ship, and that’s a valid disappointment. But what did ship is arguably more important in the long run:
- A native AI infrastructure that standardizes how AI tools connect to WordPress
- A rebuilt admin dashboard that’s faster and more modern
- Better revision tracking with visual change history
- Improved design tools including the Font Library and responsive controls
- PHP-only block development for simpler, more accessible custom builds
The platform that powers over 40% of the web just became meaningfully smarter and more design-friendly. If you build on WordPress, now is the time to get familiar with what’s under the hood — because the plugin ecosystem is about to build a lot of interesting things on top of it.
What’s your take on WordPress 7.0? Are you excited about the AI layer, or holding out for real-time collaboration? Drop a comment below.
David Daniels has been writing at DavidDaniels.com since 2001. Download the free life planning workbook, Write Open Act, to start mapping the gap for yourself.