WordPress 7.0 "Armstrong" officially shipped May 20, 2026 β marking the platform's 30th major release since version 1.0 "Miles" dropped in January 2004. The rollout was anything but smooth: a delayed launch, a last-minute feature removal, and weeks of community speculation about whether RTC (real-time collaborative editing) would make the cut. It didn't. But what did ship is arguably more consequential for WordPress's long-term architecture than any single flashy feature would have been.
Why "Armstrong"?
The release takes its name from Louis "Satchmo" Armstrong β a jazz icon who rewired an entire genre by making room for individual voice and improvisation within collaborative, orchestral structures. The parallel to what 7.0 does architecturally is deliberate: instead of AI being bolted on as a monolithic vendor-locked feature, WordPress now provides the infrastructure layer where builders bring their own models, workflows, and expression. Over 900 contributors were involved in this release, with nearly 280 of them contributing to WordPress for the first time β a meaningful signal that new blood is still flowing into the project.
The AI Stack: What Actually Shipped
Let's be clear about what 7.0 does not do: it doesn't make your site "do AI" automatically. Update and configure nothing, and your site feels identical to 6.9. No widget appears, no content gets generated β nothing happens by magic. What shipped is the wiring underneath. The WP AI Client is a new communication layer built into Core that any plugin or theme can call to send prompts to an external model without knowing which one sits on the other end. This eliminates the mess of every AI plugin bundling its own SDK and managing duplicate API keys across settings screens. The Abilities API (PHP) functions as a contract system for AI-powered capabilities β plugins register what they can do in a way both human users navigating the UI and machine agents can discover and invoke. Client-Side Abilities extend this to JavaScript, surfacing tools directly inside the editor through a built-in UI component and command palette hook rather than burying them in settings pages. The separate AI plugin β distributed independently and purely opt-in β is what actually generates output: image suggestions, title drafts, excerpt generation, alt text. The Client on its own generates nothing. Think of this as the REST API moment for WordPress AI: the power isn't in day-one features, it's in what the ecosystem builds on top over the next few years.
Connectors Screen Solves Credential Sprawl
Settings β Connectors is where provider credentials live going forward β enter your OpenAI, Anthropic (Claude), or Google (Gemini) API key once per provider, and any plugin speaking the AI Client API inherits that connection automatically. No duplicate keys across settings panels, no coordination headaches with multiple plugins from different authors. The vendor neutrality angle matters here. There's no partnership pushing you toward a specific model β your keys stay yours, and if the AI landscape shifts in two years (it will), you swap a provider connection rather than rebuilding your plugin stack. Custom providers are also supported for teams running self-hosted models.
Dashboard Refresh That Actually Needed to Happen
Spending time in the new wp-admin and then opening 6.9 in another tab felt genuinely disorienting. The gap is more noticeable than expected β tighter spacing, a cleaner color palette, smoother view transitions between screens. Nothing revolutionary individually, but together they make the admin feel like a product that was designed rather than accumulated over eighteen years of feature additions. The Command Palette (βK / Ctrl+K) is the standout addition in this release. Hit it from anywhere in wp-admin and a fuzzy-search overlay opens β type a post title, a settings screen name, or a command and you're there instantly. No sidebar navigation, no menu hierarchy, no clicking through three levels of nested pages. Once it's in your muscle memory, you'll resent every other CMS that lacks it. The Font Library deserves attention too: managing typography previously behaved differently depending on whether you were running a block theme, hybrid theme, or classic theme with no single consistent answer. 7.0 gives you one dedicated Fonts page that works across all three types β install from Google Fonts, upload your own, or remove ones you don't need. Finally. Visual Revisions transforms what was previously an impenetrable text-based diff into something actually navigable: visual markers along a scrubber let you see exactly what the page looked like at each save point and restore from there without guessing whether layout changed alongside copy.
Four New Blocks and Editor Refinements
The Breadcrumbs block is genuinely surprising this late in WordPress's life β but it's here now, with theme.json support and compatibility across all block themes. Say goodbye to Yoast breadcrumb shortcodes and custom template functions for this specific use case. The Icons block pulls from the @wordpress/icons library and lets you drop UI icons inline inside callouts, feature lists, or service grids without embedding SVGs manually or installing another plugin on every new site. The Gallery block gains a built-in lightbox and slideshow that activates on click β one of the most commonly plugin-dependent features in the editor now native. Per-Block Custom CSS is exactly what it sounds like: write CSS scoped to a single block instance right from the Advanced panel of the block sidebar, without touching global styles or child theme rules. Responsive Visibility Controls let you show or hide any block based on device size with customizable breakpoints β functionality that page builders and premium plugins have offered for years now in Core.
Developer Goodies That Lower the Barrier
PHP-Only Block Registration drops the toolchain requirement entirely for simple blocks β no npm, no webpack, no build step. Register a block entirely in PHP, and the Block API picks it up automatically. For PHP-first developers who've been avoiding the block editor because of the JavaScript overhead, this is a genuine unlock. The Site Editor now has proper routing and route validation plus a new wordpress/boot package that lets plugins register custom pages inside the Site Editor shell β no longer a closed system, plugins can build native-feeling experiences within it. Two new Interactivity API additions (watch() for state signal subscriptions and data-wp-watch as its DOM directive counterpart) address persistent headaches around reactive block development without full re-renders. WP-CLI 3.0 ships alongside with two new command groups: wp block for read-only block entity access and wp ability for interacting with the AI Abilities API from the terminal β useful early for anyone building automations or running site audits at scale.
The RTC Pull: Right Call, Hard Landing
Real-time collaborative editing was removed twelve days before launch. Concurrent editing sessions were causing race conditions in the sync layer, memory pressure wasn't where it needed to be, and fuzz testing kept surfacing bugs without clean fixes. Shipping it anyway would have been a mistake the scale of WordPress's user base tends to punish harshly. The collaborative foundation is still there β block-level Notes, the commenting system, the presence infrastructure that shows who's currently viewing a post. The multi-user simultaneous editing piece moves to a feature plugin for extended community testing before attempting another Core merge. WordPress 7.1 in August 2026 is the next candidate window, but no firm commitment has been made yet.
Breaking Changes You Need to Know Before Updating
PHP 7.2 and 7.3 are no longer supported β you need 7.4 minimum with 8.2 or 8.3 strongly recommended before touching this update. The add_theme_support('html5', array('script')) pattern is now deprecated as the script loader handles it natively. Author link title attributes are gone by default; use the new $use_title_attr parameter where needed. Patterns in fully editable mode now default to contentOnly behavior β mark content attributes with "role": "content" explicitly. backbone.js, Requests, PHPMailer, and CodeMirror all received updates that may break direct integrations.
The Bottom Line
WordPress 7.0 is a foundations release disguised as an incremental one β the AI infrastructure, Connectors architecture, extensible Site Editor, and PHP-only blocks are decisions about how WordPress works for the next several years rather than headline features you'll tweet about on launch day. Losing RTC took some wind from the launch narrative, but a rushed collaboration feature deployed to 43% of the web would have been far more damaging than a delay. The Command Palette is what you'll feel immediately; the AI Connectors screen is what will matter most in twelve months. Welcome to the Armstrong era.