WordPress 7.0 “Armstrong”: Every New Feature, What Got Cut, and What It Means for Your Site

WordPress 7.0 “Armstrong” landed on May 20, 2026 — named after jazz legend Louis Armstrong — and it’s the most consequential major release in a few years. Not because of any single feature, but because of what it sets up: native AI infrastructure baked directly into WordPress core.

TL;DR

WordPress 7.0 “Armstrong” dropped May 20. The big one: native AI infrastructure — connect OpenAI, Anthropic, or Google once, and every compatible plugin can use it. Visual revisions finally show you what actually changed instead of raw HTML diffs. Admin got a full redesign including a Command Palette (⌘K), centralized Font Library, and a new primary blue (#3858e9 — yes, it will briefly make you think something broke). Four new blocks land in core: Gallery with lightbox, Heading variations, Breadcrumbs, and Icons — all previously plugin territory. Responsive block controls let you hide/show by viewport without CSS hacks. PHP 7.4 is now the minimum — check your server before updating. Real-time collaboration was cut and deferred to 7.1.

The release was originally scheduled for April 9 at WordCamp Asia Contributor Day. Then the Real-Time Collaboration (RTC) feature hit a database architecture problem that couldn’t be patched late in the cycle — and the team made the right call to delay rather than ship something unstable. May 8, RTC was officially cut from 7.0 entirely. May 20, everything else shipped.

Here’s the full picture: what’s in 7.0, what got cut, and what you actually need to do about it.

AI Connectors: WordPress Now Talks to AI Natively

This is the headline feature — and the one most likely to change how WordPress agencies work over the next two years.

WordPress 7.0 ships a built-in AI Connectors screen under Settings. Three providers are registered out of the box: OpenAI, Anthropic, and Google. A site owner enters their API key once, and any plugin built against the new WP AI Client can use that connection. No more every plugin bundling its own SDK, its own key input, its own model calls.

The architecture has four parts: the AI Client (core PHP), the Abilities API (register named AI capabilities like “summarize” or “generate”), the JavaScript Abilities API (same thing, browser-side), and the Connectors API (the glue between plugins and providers). It’s opt-in, plugin-based — no AI features get injected automatically into your site.

We wrote a detailed breakdown of this infrastructure when it was first announced during the delay — the WP AI Client post covers how it actually works and why it matters more than the release timing drama.

Visual Revisions: Finally a Revisions Screen That Makes Sense

The old revisions screen showed raw HTML diffs. Useful if you’re a developer. Useless if you’re an editor trying to figure out what paragraph you accidentally deleted on Tuesday.

7.0 replaces that entirely. The new revisions interface renders your content as it actually looks in the editor, with color-coded change markers: yellow for modifications, red for deletions, green for additions. You scroll through saves visually, pick the version you want, and restore. One click.

For multi-author sites or any store where product descriptions go through multiple edits, this alone is worth the update.

Refreshed Admin: Command Palette, Font Library, New UI — and That Blue

The wp-admin redesign is more significant than most release notes suggest. It’s the most thorough admin theme update WordPress has shipped in years — new color scheme, cleaner palette, more whitespace, smooth transitions between screens.

Command Palette (⌘K / Ctrl+K): A fuzzy-search launcher now lives in the admin bar. Click it or hit the shortcut, type what you want — navigate to any screen, trigger any action — without lifting your hands from the keyboard. If you’ve used Linear or VS Code, you know exactly how this changes your daily workflow.

Font Library: A dedicated screen for installing, uploading, and managing fonts across block, hybrid, and classic themes. Previously scattered across theme settings and plugins. Now centralized in Appearance. This is a quiet but genuinely useful change for anyone managing design consistency across a site.

The primary color changed. Admin links and active navigation tabs moved from #2271b1 — the WordPress blue everyone has stared at for years — to #3858e9, a bolder, more electric blue that leans purple. I logged into a client site after the update and genuinely had a moment of “did someone touch the theme.” They didn’t. WordPress did. It took about 30 seconds to confirm nothing was broken and another 10 minutes to fully calm down. If you feel the same way, you’re not alone — that specific shade of blue is muscle memory at this point.

Practically speaking: if you’ve hard-coded #2271b1 anywhere in a custom admin stylesheet or child theme — check it. The color token shift is intentional and won’t be reverted.

Four New Blocks

All four previously required third-party plugins. They’re now in core:

• Gallery Block (with lightbox slideshow) — The existing gallery now supports a lightbox mode for browsing images inline without leaving the page.
• Heading Block variations — More granular control over heading markup and styling.
• Breadcrumbs Block — Proper semantic breadcrumb navigation, schema-ready, one block to drop in.
• Icons Block — A long-requested addition. Insert icons from a library directly in the editor without an icon plugin.

Each of these is a plugin you can now uninstall. Less plugin surface area means fewer update vectors and one less thing to maintain.

Responsive Block Controls

Block visibility can now be controlled per viewport — hide a block on mobile without affecting desktop, show something only on tablet, customize styles per breakpoint, and define what your custom breakpoints actually are. This replaces a category of CSS hacks and plugin-based visibility toggles for a lot of sites.

Developer Changes: PHP 7.4 Minimum and the Abilities API

The minimum supported PHP version moves to 7.4 as of this release. If you’re still running PHP 7.3 or older — check with your host before updating. Most managed WordPress hosts have been on 8.x for a while, but this is worth confirming.

The JavaScript Abilities API lands alongside the PHP-side version introduced in 6.9. Two packages ship: @wordpress/abilities for state management and @wordpress/core-abilities for the WordPress integration layer, which auto-fetches server-registered abilities via REST. This is the foundation for browser agent and WebMCP integration — and if you’re building anything on top of WordPress AI tooling, this is what you’ll be coding against.

Real-Time Collaboration: What Happened

RTC was the headline feature for most of 2025’s WordPress roadmap coverage. Google Docs-style co-editing in the block editor. It’s why the original April release got bumped — the database architecture for real-time sync had a performance problem that wasn’t patchable late in the cycle.

On May 8, the core team officially removed RTC from 7.0 entirely. The reasoning was sound: ship it properly or don’t ship it. It’s now scheduled for re-evaluation during the 7.1 release cycle.

What shipped instead as the primary collaboration feature: Block-level Notes — a comment/annotation system tied directly to individual blocks. Not Google Docs, but genuinely useful for editorial workflows on multi-author sites.

How to Update Safely

Standard update hygiene applies. Back up first. Test on staging if you’re running a business-critical site. The things most likely to cause compatibility issues: PHP 7.4 requirement, any plugins that hooked into the old revisions screen, and anything that bundled its own AI SDK that now conflicts with the new WP AI Client.

You can review the full technical notes in the WordPress 7.0 Developer Notes on Make WordPress, and the official release announcement is on WordPress.org News.

7.0 is a release worth taking seriously — not because any single feature is a dramatic upgrade, but because the AI infrastructure layer it establishes is going to shape what WordPress looks like for the next several major versions.