WordPress 7.0 “Armstrong” Is Here: AI Lands in Core

🇹🇷 Türkçe: Bu yazının Türkçesini oku →

There’s a new milestone for the WordPress community, and I want to walk you through it properly. Before the feature tour, though, let me give you the consultant’s version of the AI conversation everyone is having right now — because it changes how you should read this release.

Everyone is talking about building a website with AI. You can, and it works. But we could already build sites quickly with simple tools years ago. The new tools are more powerful and genuinely easy to use — I understand the appeal. My advice is unchanged: think twice before you reach for something brand new — a new CMS, a shiny AI site builder — just to publish what is, in the end, a fairly ordinary website.

Running a website was never the easy part, and SEO is harder than it was, because there is a new content monster in the room. Your URLs, your slugs, your rankings, your indexed pages — these still decide whether the site earns anything. Stand on a mature CMS. That is not nostalgia; it is risk management.

And you can run WordPress and AI together — that part is simple. The difference shows up later. When it starts to work — the first ten thousand visitors arrive and you suddenly need analytics, redirections, view counts, revision history, and a hundred other things — the AI-generated pages will not give you what WordPress does. AI itself works by leaning on a deep, accumulated knowledge base to solve your problem. So do what AI does: lean on accumulated maturity. Why start from zero on a new CMS, or no CMS at all, when WordPress already hands you exactly that? With that framing, here is what 7.0 actually brings.

WordPress 7.0 “Armstrong” landed on May 20, 2026. It was originally slated to debut at WordCamp Asia in Mumbai on April 9, but the core team postponed the date after spotting a critical architectural issue. The result is one of the most ambitious WordPress releases in years: more than 419 core Trac tickets, over 300 bug fixes, and 400+ editor-side improvements. Here’s what 7.0 brings, from both a site owner’s and a developer’s point of view.

AI is now a WordPress capability

The headline of 7.0 is that AI has graduated from being a plugin feature to a part of core itself. The new WP AI Client lets plugins talk to generative AI models in a provider-agnostic way, with WordPress core handling request routing. Developers can use the using_model_preference() function to specify models in order of preference, then add feature detection to match capabilities against available models—lowering cost and speeding up processing.

A new Settings > Connectors screen manages all of this in one place, shipping with three default providers: Anthropic, Google, and OpenAI—and you can add your own. A client-side Abilities API turns AI abilities into workflows that run one after another. Important note: AI features are off by default; enabling them is entirely your call.

Read the design of that carefully, because it is the smart part. WordPress did not bet the release on one AI vendor. It shipped a provider-agnostic client and a routing layer, so the thing that changes fastest in this industry — which model is best this quarter — sits behind an interface you can swap. That is the opposite of lock-in, and it is exactly why core belongs in this position and a single-vendor site builder does not.

Why “AI in core” is not the same bet as “an AI builder”

Let me put my age on the table, because it earns me the right to this caution. I have built on the shiny new runtime before, and I have watched it die with the whole industry standing on top of it.

My generation of interactive work ran on Macromedia Flash and ActionScript. For a decade it was the platform — games, whole sites, product configurators, entire agencies staffed around it. It was faster to build in than anything else and everyone told you it was the future. Then a single letter from Steve Jobs and a shift to mobile ended it, and a decade of source files became unmaintainable overnight. The people who survived that were not the ones who had bet hardest on Flash. They were the ones who had kept their content, their structure, and their URLs in something portable, and treated the runtime as a layer they could replace.

That is the exact distinction that matters here. “AI in core” is a portable interface you own; your content stays in the WordPress database, and the model behind the connector is replaceable. “Build my whole site in an AI builder” is Flash again — a runtime somebody else controls, holding your content in a shape you cannot export cleanly the day the vendor pivots. Use the AI. Do not hand it the deed to the house.

A modernized dashboard

WordPress 7.0 delivers the most significant admin refresh in years. The new color scheme, named “Modern,” brings higher contrast, refreshed typography, and a cleaner interface. Highlights:

• Command Palette shortcut: A ⌘K / Ctrl+K icon in the upper admin bar gives you access to tools from anywhere in the dashboard.
• View Transitions: Smooth sliding transitions between admin screens, automatically disabled if “reduced motion” is set.
• Font Library: A dedicated, central page to upload and manage fonts.
• Visual Revisions: Compare two revisions visually in the editor with a slider, plus color-coded change indicators.

Design agility: new blocks and tools

Design tooling got a notable boost in 7.0. The most talked-about addition is per-block custom CSS: you can now write custom CSS that applies only to a single block instance. New blocks and improvements in this release:

• Heading block: A new block with variations for all heading levels, quick transforms, and easy toggling in the inspector.
• Breadcrumbs block: Automatically reflects your site’s navigational hierarchy and can be applied globally in site parts like the header. Great for SEO.
• Icon block: Add SVG icons directly into content with color, size, and border controls.
• Gallery block: Lightbox support with a slideshow option (“enlarge on click”).
• Cover block: You can now embed video as a section background.
• Paragraph block: Columns layout and text indent (textIndent) support.

Mobile and responsive editing

7.0 introduces device-based block visibility: hide a block on phones but show it on desktop, or define styles for different breakpoints—without writing a line of CSS. Blocks with visibility rules are flagged with icons in List View. Mobile hamburger menu overlays can now be fully customized from blocks and patterns in the Site Editor.

What’s in it for developers?

• PHP-only block registration: Blocks and patterns can now be created server-side in pure PHP and registered with the Block API, with automatic registration via autoRegister.
• Interactivity API: A new watch() function that subscribes to changes in any signal accessed in a callback, plus the data-wp-watch directive.
• DataViews & DataForms: A new Activity layout, Details layout, improved modals, and third-party type registration in the Field API.
• Block Bindings & Pattern Overrides: Pattern overrides now apply to any block, including custom blocks.
• Site Editor foundation: Extensible routing, a new @wordpress/boot package, and a refactored @wordpress/scripts that reduces Webpack dependence.

Security, multisite, and PHP requirements

An important security change: the Administrator and Editor roles were removed from the default new-user role selector, and Site Health warns if one of them was selected before updating. The default_role_dropdown_excluded_roles filter lets you customize this. Good news for multisite users: networks and sites are no longer automatically marked as spam when an account is flagged as spam.

On the infrastructure side, WordPress core’s minimum PHP version is now 7.4 (support for PHP 7.2 and 7.3 has been dropped); PHP 8.x is recommended for best performance. PHPMailer was updated to 7.0.2 and CodeMirror to v5.

Before you update

As with every major release, test on a staging environment first. Make sure your PHP version is at least 7.4, check your themes and plugins for 7.0 compatibility, and take a full backup. The iframed editor is now enforced when all blocks use Block API v3 or higher; backward compatibility is preserved for older blocks. If you won’t be using AI features, you can simply leave the Connectors screen as-is (disabled).

Here is what I would actually do with 7.0. Update on staging, take the admin refresh and the security role change as pure wins, and leave the Connectors screen off until you have a concrete job for it — a caption generator, an alt-text pass, a draft-summariser — rather than switching AI on because it is there. When you do turn it on, start with one provider, one ability, one workflow, and measure the cost before you widen it. The whole design of the AI Client rewards that patience: because the model sits behind a preference list, the restraint costs you nothing later.

WordPress 7.0 “Armstrong” modernizes the editor and dashboard experience while laying a solid foundation that carries WordPress into the AI era. Ready to update your site? Share your questions in the comments.