On May 20, 2026, WordPress shipped version 7.0, codenamed "Armstrong." It is the first major release of the year and the one that finally treats AI as a core platform feature instead of something every plugin figures out on its own. If you run a WordPress site — or build them for clients — the AI infrastructure alone is worth understanding before you hit "update."

The Connectors API changes the plugin game

Until now, every WordPress plugin that used AI needed its own API key, its own connection logic, and its own way of handling errors. If you had an SEO plugin talking to OpenAI, a translation plugin talking to Google, and a chatbot plugin talking to Anthropic, you were managing three separate integrations with three separate billing setups. It worked, but it was messy.

WordPress 7.0 introduces two new layers built on top of the Abilities API from 6.9: the Connectors API and the WP AI Client SDK. The Connectors API is a standardized framework for managing external service connections. Right now it focuses on AI providers, but the architecture is designed to handle other external services down the road. The WP AI Client SDK is a WordPress-native library — wordpress/wp-ai-client — that gives developers a single, consistent interface to talk to multiple AI providers. It uses the WordPress HTTP API under the hood and plugs directly into the Abilities API to expose WordPress-specific functions to AI models.

What this means in practice: a plugin author can now build AI features without wiring up their own provider connections. They call the SDK, the SDK talks to whatever provider the site admin has configured, and the site admin manages one set of credentials instead of a dozen. For agencies managing multiple client sites, this is a significant reduction in complexity.

The admin got a real facelift

The visual refresh in 7.0 is not a radical redesign, but it is noticeable. There is a new default color scheme, updated buttons and input fields, and a cleaner overall feel. The command palette — which has been gaining features over the last few releases — is now accessible everywhere in the admin. If you have been using keyboard shortcuts to navigate the block editor, that workflow now extends to the rest of the dashboard.

The bigger design win is customizable navigation overlays. WordPress has been terrible at mobile menus for years. You either lived with whatever your theme gave you or installed a heavyweight plugin to get something decent. In 7.0, navigation overlays are fully customizable template parts. You can design exactly what happens when someone taps the hamburger menu on their phone — add social icons, a search bar, a contact form, whatever fits. Images in the overlay are automatically deprioritized to protect the page's loading speed, so you do not have to worry about a fancy menu killing your Core Web Vitals.

This feature was clearly inspired by Mike McAllister's Ollie Menu Designer, which proved the block editor could handle complex menus if core gave it the right framework. Core finally did.

Content-only editing protects your designs

If you have ever handed a WordPress site to a client and watched them accidentally destroy a carefully built hero section by dragging blocks around, 7.0 has a fix. The new "content-only" mode for patterns lets you lock the structure and styling of a design pattern while keeping the text, images, and links editable. Your client can swap out the headline and the photo without touching the layout. If they need deeper access, they can click "edit pattern" to unlock everything.

This is a small feature with big implications for agencies. It means you can ship complex page designs and trust that routine content updates will not break them. No more frantic calls about "the homepage looks weird."

What to do before you update

WordPress 7.0 is a major version bump. The core team has done extensive testing, but the React 19 situation from earlier this month — where Gutenberg 23.3 shipped React 19 and reverted it two days later after plugin breakage — is a reminder that major updates deserve caution.

Test on a staging site first. Check your plugins, especially anything that touches the block editor or uses custom React components. The Connectors API is additive and should not break existing integrations, but the admin redesign and navigation overlay changes could conflict with custom admin CSS or theme customizations.

The release is stable and the improvements are worth it. Just do not skip the staging step.

The bottom line

WordPress 7.0 is less about flashy features and more about laying groundwork. The Connectors API positions WordPress as a platform where AI features are native infrastructure, not bolted-on extras. The admin refresh and navigation overlays fix long-standing pain points. Content-only editing makes the block editor safer for non-technical users.

If you have been waiting for a reason to update, this is a good one. If you have been wondering whether WordPress is still relevant in the age of AI website builders, version 7.0 is WordPress's answer: we are not just relevant, we are building the plumbing.