What’s New in WordPress 7.0? A Detailed Look at the Armstrong Release

WordPress 7.0 was released on 20/05/2026 under the codename Armstrong. This is the first major release after the 6.9 branch, and it is also the version where WordPress pushes AI foundations into Core much more clearly. If you manage a website, work on content, or develop plugins, this update is worth reviewing carefully before you hit the upgrade button.

I reviewed the release archive, the official announcement, and the WordPress 7.0 field guide to pull together the most important changes in this article. The goal is to help you quickly see what is new in 7.0, which parts are worth trying right away, and which parts should go to a staging environment first.

• Release date: 20/05/2026
• Codename: Armstrong, named after jazz artist Louis Armstrong
• Main highlights: AI foundations in Core, a new dashboard, and better design tools and editorial workflows
• Groups that should care most: website admins, content teams, WordPress agencies, and plugin or theme developers

What changed in WordPress 7.0 compared to 6.9?

At a glance, 7.0 is an upgrade focused on day-to-day work experience. WordPress 6.9 laid the groundwork for Notes and the Abilities API. In 7.0, the Core team pulls more of those pieces together into a clearer toolkit: there is a connection management screen, an AI Client, a command palette in the admin bar, visual revisions, and several new blocks for building interfaces.

Category	WordPress 6.9	WordPress 7.0
AI in Core	Only the Abilities API foundation was in place	Includes AI Client, Connectors screen, and client-side abilities
Admin experience	Stable, focused on smaller improvements	New admin interface, view transitions, and a command palette in the admin bar
Content editing	Notes and better collaboration	Visual revisions, editable patterns as a single block, and responsive editing
Interface design	Continued improvements to the block editor	Navigation overlay, Icon block, Breadcrumbs block, and custom CSS per block
Developers	Many APIs had already been opened up	Adds PHP-only block registration, routing for the Site Editor, and a broader Interactivity API

The most practical point, in my view, is that WordPress 7.0 does not try to cram in too many features just for show. The new work is focused on the places users open every day: the admin area, the editor, and the publishing workflow.

ℹ️ According to the WordPress.org release archive, 7.0 is the latest stable release in the 7.0 branch and was officially released on 20/05/2026.

How is AI starting to enter WordPress Core?

This is the easiest part of WordPress 7.0 to misunderstand. The release does not turn WordPress into a CMS where every site suddenly gets built-in AI writing buttons out of the box. What Core mainly adds is the infrastructure for plugins and features to use AI in a standardized way, including the WP AI Client, Settings > Connectors, and the client-side Abilities API.

Where is AI in WordPress 7.0 actually used?

• In the admin area: site owners go to Settings > Connectors to configure API keys for OpenAI, Google, or Anthropic.
• Inside the official AI plugin or third-party plugins: features such as title suggestions, excerpt generation, alt text suggestions, image generation, or content classification can all run through the shared WP AI Client layer.
• Inside plugin PHP code: developers can call the official server-side API through wp_ai_client_prompt().
• Inside JavaScript admin interfaces: developers can load @wordpress/core-abilities or @wordpress/abilities to work with abilities on the client side, such as navigation, block insertion, or executing registered abilities through the REST API.

In other words, regular users will mainly notice AI through the Connectors screen and through plugins that adopt this new foundation. Developers will care more about the fact that the API is now standardized.

What is WP AI Client?

According to the official WordPress dev note, wp_ai_client_prompt() is the main entry point for AI tasks in PHP. A plugin describes the prompt, model preference, or output format. WordPress then routes the request to a suitable provider from the connectors that the administrator has already configured.

ℹ️ The practical benefit here is that plugins do not need to manage API keys themselves. Credential handling goes through the Connectors API, so permissions and key storage are centralized.

PHP example from the official WordPress 7.0 docs

The example below follows the dev note Introducing the AI Client in WordPress 7.0. This is how a plugin can call text generation through the official Core API:

$text = wp_ai_client_prompt( 'Write a haiku about WordPress.' )
    ->generate_text();
if ( is_wp_error( $text ) ) {
    // Handle error.
    return;
}
echo wp_kses_post( $text );

If a plugin wants to prefer specific models, the WordPress documentation also provides an example using using_model_preference():

$text_result = wp_ai_client_prompt( 'Summarize the history of the printing press.' )
    ->using_temperature( 0.1 )
    ->using_model_preference(
        'claude-sonnet-4-6',
        'gemini-3.1-pro-preview',
        'gpt-5.4'
    )
    ->generate_text_result();

This needs to be read correctly: this is an API for plugin developers, not a code snippet that end users paste into the admin area and start using directly.

What is the Connectors screen for?

The Connectors screen is where administrators connect AI providers. According to the Introducing the Connectors API in WordPress 7.0 dev note, WordPress 7.0 ships with three featured connectors: Anthropic, Google, and OpenAI. This is where you install the provider plugin, enter the API key, and review connection status. Developers can use functions such as wp_is_connector_registered(), wp_get_connector(), and wp_get_connectors() to inspect the registry.

if ( wp_is_connector_registered( 'anthropic' ) ) {
    // The Anthropic connector is available.
}
$connector = wp_get_connector( 'anthropic' );
if ( $connector ) {
    echo $connector['name']; // 'Anthropic'
}

⚠️ It is important to keep the scope clear: WordPress 7.0 lays the AI groundwork in Core. Features such as title generation, image generation, or alt text suggestions still live in the official AI plugin or third-party plugins built on top of this foundation. Core does not automatically enable all of them for every site.

When is the client-side Abilities API used?

This part is mainly for JavaScript inside the admin experience. According to the Client-Side Abilities API in WordPress 7.0 dev note, a plugin can enqueue @wordpress/core-abilities when it wants to use abilities registered on the server, or use @wordpress/abilities alone when it wants to register client-side abilities for a custom screen.

add_action( 'admin_enqueue_scripts', 'my_plugin_enqueue_abilities' );
function my_plugin_enqueue_abilities() {
    wp_enqueue_script_module( '@wordpress/core-abilities' );
}

import { executeAbility } from '@wordpress/abilities';
try {
    const result = await executeAbility( 'my-plugin/create-item', {
        title: 'New Item',
        content: 'Item content',
        status: 'draft',
    } );
    console.log( 'Created item:', result.id );
} catch ( error ) {
    console.error( 'Execution failed:', error.message );
}

This JavaScript example fits custom admin workflows, such as creating an item, navigating to a settings page, or inserting a block. It is not a direct prompt API for a public frontend. The AI Client documentation also stresses a safer pattern: build specific REST endpoints for each AI feature, then let JavaScript call those endpoints, instead of allowing arbitrary prompts from the client.

What does the content team gain?

If you work on content, the benefit is not really that “AI solves everything.” The real gain is that governance becomes cleaner: API keys live in Connectors, multiple plugins can share one foundation, and the technical team gets a more manageable permission model. For large WordPress sites, that is more practical than a few isolated generate buttons.

If you want a clearer picture of the AI foundation and how it affects websites, you can also read What is Generative AI? on the AZDIGI blog to get the context before real deployment.

How are the dashboard, editor, and design tools changing?

This is the group of changes that regular users will notice right after logging in. WordPress 7.0 refreshes the admin interface with a Modern tone, adds page transition effects, places the command palette button in the admin bar, and improves quite a few areas in the editor.

1. Visual Revisions

Previously, you mostly reviewed revisions through text diffs. Version 7.0 lets you drag a timeline to compare changes in a more visual way. For editorial teams with many contributors, this helps review edits faster, especially on landing pages or long articles with many blocks.

2. Font Library for every theme

Font Library is no longer limited to block themes. According to the feature showcase page, WordPress 7.0 opens font management to block, hybrid, and classic themes. For agencies or in-house teams maintaining many older sites, this is far more practical than forcing a theme switch.

3. Responsive Editing Mode and new blocks

Page builders get more control over how blocks appear on different devices. You can hide or show blocks by desktop, tablet, or mobile directly inside the editor. There is also an Icon block, a Breadcrumbs block, a gallery lightbox, and a navigation overlay canvas for building menus more flexibly.

Anyone optimizing WordPress performance should also look at this from a practical angle. Easier interface building does not mean the site automatically becomes faster. After upgrading, you should still review cache, images, and server configuration. These two articles, configuring LiteSpeed Cache for WordPress and slow WordPress on VPS, will be useful if you want to maintain speed after the update.

💡 If you are building a new site, WordPress 7.0 is a good fit for testing in a staging environment first. You can install it quickly with Docker Compose or LEMP on Ubuntu 22.04 to test plugins and themes more safely.

What should developers and site owners keep in mind before upgrading?

WordPress 7.0 includes many new parts, but not every site should update on day one. For sites with many plugins, custom themes, or daily revenue coming in, I lean toward a controlled upgrade approach.

• Back up the entire site: include files, database, and cache configuration.
• Test on staging: check the theme, page builder, forms, SEO plugins, and WooCommerce if used.
• Review plugins related to AI or the editor: this is the group most likely to be affected when Core adds new APIs and interface changes.
• Measure performance again after the update: check Core Web Vitals, slow queries, lazy-loaded images, and cache.
• Review the editorial workflow: if your team relies heavily on revisions, start testing visual revisions early so people can get used to it.

For developers, the 7.0 field guide is more useful than the general overview post. It lays out the changes quite clearly around PHP-only block registration, the Interactivity API, block bindings, the plugin list filter, routing for the Site Editor, and some security updates such as tighter user registration flows.

If your site is just a standard content blog with few plugins and you already keep WordPress updated regularly, moving to 7.0 will probably be fairly smooth. But if you run an ecommerce site or a high-traffic website, move it to staging, test it, and only then push to production. The article Installing and setting up a WordPress website is also useful if you need to review the basics before upgrading.

🚫 Do not update directly on a live website that is running ads or receiving orders continuously if you have not tested payment plugins, forms, cache, and the theme. A small editor or layout issue can be enough to hurt conversions.

Should you upgrade to WordPress 7.0 right now?

The short answer is: yes, but follow a rollout plan. WordPress 7.0 is a notable release because it opens a new direction for AI in the WordPress ecosystem, while also fixing several pain points in the admin area and editor. If you work with websites for the long term, you will eventually need to get familiar with these changes.

If you need a stable environment to run WordPress after the upgrade, AZDIGI offers WordPress Hosting already optimized for content websites, blogs, and small business sites. For websites with more plugins or broader resource needs, Premium Business Hosting or X-Platinum VPS will be a better fit because they give you more control over performance and scaling as traffic grows.

In the end, WordPress 7.0 is not an update to look at casually. It changes how WordPress prepares for AI, how content teams work inside the editor, and how developers will extend the system later on. If you manage a WordPress website every day, this is a release where the notes are worth reading carefully before you update.