WordPress 7.0 “Armstrong”: What’s New (and What Got Pulled)

WordPress 7.0 “Armstrong” shipped on May 20, 2026, the first major release of the 7.x series and the 30th major version of WordPress since 1.0 “Miles” in January 2004. Release lead Matias Ventura and a global team of 875+ contributors (including 200+ first-time contributors) landed 420+ enhancements and fixes across Core and Gutenberg.

The headline framing from the release announcement: “WordPress 7.0 marks the start of a new era, laying the foundation for AI across the WordPress experience.” AI integration in Core, a modernized dashboard, four new blocks, server-side block registration, and the headline feature that didn’t ship (real-time collaboration, pulled May 8) are the story.

The Headline: AI Comes to WordPress Core

The biggest shift in 7.0 is that WordPress Core can now talk to AI models natively. There are four moving pieces:

• AI Client (Core). A new client built into WordPress that handles communication with generative AI models. Plugins, themes, and Core features can use it without bundling their own SDKs.
• Abilities API (server). A PHP-side API for registering specific AI-powered “abilities” (generate, summarize, suggest, etc.) and exposing them to other parts of WordPress.
• Client-Side Abilities (JavaScript). The JS counterpart to the Abilities API, with a built-in UI and a command palette so abilities can be invoked from anywhere in the editor.
• Connectors screen. A central dashboard hub for managing external AI service connections. Ships with three presets to get started, and supports your own connections with a few clicks of authentication.

By itself, the AI Client doesn’t generate anything; it’s the plumbing. To actually generate images, titles, excerpts, or alt text, you install the new optional AI plugin that sits on top of the Client and Abilities API. The plugin is opt-in, so a stock 7.0 install is no more or less AI-y than a stock 6.9 install until you turn it on.

For developers, the real win is that the Abilities API gives you a single, opinionated place to plug AI features into without writing your own OpenAI or Claude or whoever-else wrapper. If you’ve ever shipped an AI feature in WordPress before, you know how much of that code has been re-invented across plugins. 7.0 consolidates that into Core.

The Headline That Didn’t Ship: Real-Time Collaboration

Real-time collaboration was supposed to be the marquee feature of 7.0. Multiple editors in the same post simultaneously, the way Google Docs handles concurrent editing. It had been in development for several release cycles, with parts of the infrastructure (block notes in 6.9, presence APIs) landing incrementally.

On May 8, twelve days before release, Matt Mullenweg pulled the feature. The official reasons: “concerns around surface area, race conditions, server load, memory efficiency, and recurring bugs found through fuzz testing.” RTC isn’t shelved permanently; the team is preparing a feature-plugin testing phase before another Core merge attempt in a future release.

If you want the full background on why RTC was removed and what it means for the WordPress roadmap, we covered it in detail: Real-Time Collaboration Removed from WordPress 7.0.

The Modernized Dashboard

The wp-admin you log into on a fresh 7.0 install looks meaningfully different from 6.9. Most users will notice this first, before any of the AI stuff.

• New color scheme and finishes. Cleaner palette, more whitespace, smooth transitions between screens. The most thorough admin theme update WordPress has shipped in a long time.
• Command Palette. A new Cmd+K (or Ctrl+K) shortcut in the admin bar opens a fuzzy-search palette that jumps you anywhere in the dashboard. Borrowed from dev tools like VS Code and Linear, and it’s the single change you’ll feel most often once you’re used to it.
• Font Library. A dedicated screen for installing, uploading, and managing fonts across block, hybrid, and classic themes. Previously fragmented across theme settings and plugins; now centralized.
• Visual revisions scrubber. The Revisions screen now shows visual markers indicating what actually changed at each save point. Easier to find the version you want without diffing text walls.
• Iframed editor enforced for v3 blocks. When every block on a page uses Block API v3 or higher, the post editor now runs inside an iframe by default. This fixes a long-standing class of CSS bleed issues between admin and editor styles.

New Blocks and Editor Improvements

Four new blocks shipped, plus meaningful upgrades to existing ones.

• Gallery (lightbox). The Gallery block now supports a lightbox slideshow mode out of the box. No plugin required.
• Heading block (refined). A reworked Heading block with cleaner markup output and granular control over heading-level styles.
• Breadcrumbs. A native Breadcrumbs block. Until 7.0, breadcrumbs meant Yoast, Rank Math, or a custom shortcode. Now it’s a Core block with theme.json styling support.
• Icons. A native Icons block with a library of common UI icons. Useful for feature lists, callouts, and anywhere you’d previously embedded SVGs by hand.

Beyond the new blocks, four editor-wide upgrades are worth flagging:

• Block-level custom CSS. You can now apply custom CSS to any individual block, right in the editor sidebar. No more child theme just to style one section.
• Responsive controls. Hide or show blocks per device (desktop, tablet, mobile), adjust styles for different breakpoints, and customize what those breakpoints are. The kind of thing site builders have wanted in Core for years.
• Block-based menu overlay. The mobile menu overlay is now fully customizable with blocks and patterns. Add columns, custom typography, an embedded close button, or whatever else the design calls for.
• Patterns as single units. Patterns now act as a single unit by default with detachable elements for isolated control, plus a contentOnly mode where developers mark which attributes are editable content vs design scaffolding.

What’s New for Developers

7.0 is the biggest developer release in a while. The headline items:

• PHP-only block registration. Blocks and patterns can now be registered server-side using only PHP, auto-registered through the Block API. The JavaScript build pipeline isn’t required for simple blocks anymore, which lowers the barrier for plugin authors who don’t want to set up webpack/wp-scripts just to ship a couple of blocks. Lives nicely next to other PHP-only customizations you’d put in functions.php or a custom plugin.
• Extensible Site Editor. The Site Editor now exposes a routing layer with route validation, plus a new wordpress/boot package that lets plugins build custom Site Editor pages. The Site Editor is no longer a fixed set of screens; it’s a platform that plugins can extend.
• Interactivity API additions. A new watch() function (subscribe to signal changes) and a data-wp-watch DOM directive for lifecycle reactions. Useful for blocks that need to respond to state changes without re-rendering.
• Block bindings. A new block_bindings_supported_attributes filter lets you control which attributes on a custom block can be overridden by Pattern overrides.
• Scripts can depend on modules. The script loader now allows traditional scripts to declare dependencies on ESM modules, smoothing the JS-to-modules transition.

Minimum requirements

PHP 7.4 is now the minimum. WordPress 7.0 drops support for PHP 7.2 and 7.3. If you’re on shared hosting that hasn’t been touched in years, check your PHP version before updating. Site Health flags this directly. Most major hosts default to PHP 8.1 or 8.2 for new sites, so this only bites legacy hosting setups.

Library updates

• backbone.js → 1.6.1
• Requests → 2.0.17
• CodeMirror → v5 (with ESLint and CSSLint updates; Esprima replaced with Espree)
• PHPMailer → 7.0.2

Removals and Deprecations

If you maintain a plugin or theme, these are the breaking changes to know:

• Real-time collaboration. The biggest “deprecation” is that RTC never landed. If your roadmap assumed it would, plan around a future release timeline (no version target has been announced).
• HTML5 script theme support removed. Themes that used add_theme_support( 'html5', array( 'script' ) ) need to drop that argument. The script loader handles HTML5 script output natively now.
• Title attributes removed from author link functions by default. Functions like get_the_author_link() no longer add a title attribute. There’s a new $use_title_attr parameter if you specifically need it back.
• Pattern contentOnly defaults. Patterns default to contentOnly mode now. If you’ve built blocks that rely on patterns staying fully editable, set "role": "content" on the content attributes to avoid them being hidden from editors.

Should You Update?

The honest answer for most sites: not on day one. WordPress major releases generally settle in over a 7-to-14-day window as plugin and theme authors push compatibility patches. Even when a release is well-tested, the combination of your specific stack rarely matches the testing matrix exactly.

A safe update timeline:

1. Day 0 (May 20). Update a staging copy of your site. Run through your most-used flows. Note anything that breaks.
2. Days 1-7. Watch your plugin update feed. Most active plugins will ship a 7.0-compatible release in this window. If a critical plugin hasn’t, that’s your signal to wait.
3. Days 7-14. If staging is clean and your plugins are updated, push to production. Take a full backup first (you should be doing this anyway).
4. If you’re on PHP 7.2 or 7.3. Don’t update WordPress yet. Update PHP first, in a staging environment, then update WordPress. Updating both at once gives you two failure modes to debug instead of one.

The exception: if you’re spinning up a brand-new site, install 7.0 directly. There’s no upside to starting on 6.9.

How to Update to WordPress 7.0

1. Full backup. Files and database. Use UpdraftPlus, Solid Backups, or your host’s snapshot tool. Verify the backup downloads before you touch anything.
2. Test on staging. Most managed hosts (WP Engine, Kinsta, SiteGround, Cloudways) include one-click staging. Use it. If you don’t have staging, a local copy via Local or DevKinsta works too.
3. Update plugins and themes first. On the staging copy, update everything to its latest version before you touch WordPress core. Plugins that aren’t yet 7.0-compatible will throw warnings here, not after Core updates.
4. Run the WordPress 7.0 update. Dashboard > Updates > Update to 7.0. Or from the command line, wp core update --version=7.0 via WP-CLI.
5. Resave permalinks. Settings > Permalinks > Save Changes. Regenerates rewrite rules in case anything shifted. Belt and suspenders.
6. Smoke-test the front-end. Visit your homepage, a post, a category archive, and any custom flow that matters to your business. Check the editor too.
7. Push to production. When staging is clean, repeat the update on the live site. Or sync staging up if your host supports it.

The Codename: Why “Armstrong”?

Every WordPress major release since 1.0 has been named after a jazz musician. The tradition started with 1.0 “Miles” (Miles Davis) in January 2004 and has continued through 30 major versions: 6.9 was “Gene Harris,” 6.8 was “Cecil” (Cecil Taylor), 6.7 was “Rollins” (Sonny Rollins), and so on.

7.0 honors Louis “Satchmo” Armstrong, the jazz trumpeter widely credited as the “first great jazz soloist.” Armstrong is the figure who transformed jazz from an orchestral art form into a solo art form, introduced improvisation as a central element, and influenced essentially every artist who came after him. From the release announcement: “Louis Armstrong wove his personal touch into the world of Jazz. With WordPress 7.0 ‘Armstrong,’ you can build with yours.”

For the full naming history (every version from 1.0 “Miles” to 7.0 “Armstrong” with what each one shipped), see our WordPress Version History.

Frequently Asked Questions

Wrapping Up

WordPress 7.0 “Armstrong” is the start of an AI-integrated WordPress and the end of a long road for real-time collaboration. The AI plumbing is the biggest structural change in years. The dashboard refresh is the most visible. The Command Palette is the change you’ll feel daily. And the RTC removal is the story of how WordPress chose stability over its own headline feature.

For deeper context: the official announcement, the field guide (developer-focused), our RTC removal breakdown, and the full WordPress version history from 1.0 “Miles” forward.