On May 20, 2026, WordPress officially launched its major update, WordPress 7.0 "Armstrong". Named after the legendary jazz solo artist Louis Armstrong, this version marks a major turning point in WordPress history. The defining feature is the native integration of AI features directly into the core, standardizing what was previously entirely dependent on third-party plugins.
This article organizes the architectural shifts in WordPress 7.0 and analyzes the story behind the 1.5-month delay (moving from the original April 9 target to the final May 20 release) based on official Core team announcements.
[!NOTE]
This article is compiled as of May 2026, based on the WordPress 7.0 "Armstrong" Official Release Announcement, the WordPress 7.0 Field Guide, the WordPress Roadmap, The Path Forward for WordPress 7.0, and Extending the 7.0 Cycle.
What's New? Major Updates in WordPress 7.0
The WordPress 7.0 release introduces extensive system overhauls and new features. Below are the key changes.
1. AI Foundations (Core AI Integration)
The most prominent feature of WordPress 7.0 is the introduction of the AI Client and Abilities API into the core, standardizing AI integrations. According to the release announcement, a new Connectors screen has been added to the dashboard, enabling centralized management of API keys for providers like OpenAI and Anthropic.
By installing optional official AI plugins, users can now execute the following tasks directly in the editor:
- Auto-generating titles and excerpts
- Generating and editing featured images
- Auto-suggesting image alt text (
alt)
Furthermore, the JavaScript layer now includes the Client-Side Abilities package to control interactive UIs and the command palette.
2. Dashboard Modernization
This update features a refreshed dashboard UI with smooth fade transitions and a permanently accessible command palette. Invoked by Ctrl+K (⌘K on macOS), the command palette drastically reduces the clicks needed to navigate to settings, posts, and various tools.
3. Font Library Expansion and Block Controls
The Font Library feature, which was previously exclusive to Block Themes (FSE), is now available to all themes, including classic and hybrid themes. This is a highly anticipated improvement for many site owners.
Editor expressiveness has also been steadily enhanced with responsive block controls (toggling block visibility based on screen sizes) and the ability to manage nested blocks as a single "Pattern" for unified placement and styling.
The Architecture's Philosophy: Standardizing AI with the Abilities API
Looking at the design of WordPress 7.0, there is a clear intention to go beyond simple convenience and define what an open-source platform should look like in the age of AI.
Previously, AI plugins established independent connections to external APIs, raising security and performance concerns. WordPress 7.0 addresses this by laying down a unified Connectors framework in the core, securing data transmissions while creating an extensible ecosystem for plugin developers.
The following diagram illustrates the data flow of AI features in WordPress 7.0.
flowchart TB
classDef default fill:#fafafa,stroke:#cccccc,stroke-width:1px,rx:4px,ry:4px;
classDef core fill:#eef2f7,stroke:#99b3cc,stroke-width:1.5px,rx:6px,ry:6px;
classDef ext fill:#fff5e6,stroke:#e6b89c,stroke-width:1px,rx:4px,ry:4px;
UI("エディタ・UI層 / コマンドパレット"):::default
CoreAI("Core: AI Client & Abilities API"):::core
Conn("Core: Connectors Hub"):::core
ExtAI("外部AIプロバイダー / OpenAI・Anthropic等"):::ext
Plugin("サードパーティ製プラグイン"):::default
UI --> CoreAI
Plugin --> CoreAI
CoreAI --> Conn
Conn --> ExtAI
With this architecture, developers no longer have to worry about individual API changes from AI providers. Instead, they can simply tap into the unified Abilities API to build sophisticated AI-driven plugins. It is a brilliant approach that balances "standardizing the infrastructure" and "democratizing extendibility"—very typical of WordPress.
Why the 1.5-Month Delay? The Story Behind Excluding Collaborative Editing
WordPress 7.0 was initially slated for an April 9, 2026 release, but was ultimately pushed back to May 20. Let's analyze the background of this delay objectively, referencing official reports from the Core team.
1. The Decision to Postpone Collaborative Editing
According to the "The Path Forward for WordPress 7.0" published on April 2, 2026, the team realized that rushing real-time collaborative editing (the centerpiece of Phase 3) into the 7.0 release carried too high of a quality risk. As a result, collaborative editing was postponed to a future release to ensure the stability of the other major features.
Rather than "pushing everything in just to meet the deadline," the team prioritized quality over scope—a decision that was highly sensible from a user's perspective.
2. Extending the Release Cycle
On March 31, 2026, the "Extending the 7.0 Cycle" post announced that the overall release cycle would be extended to dedicate extra time to bug fixing and polish.
Since 7.0 touched extensive areas—AI infrastructure, the dashboard UI, and the editing experience—it was only natural to prioritize the stability of the integrated system over speed.
3. Prudence in Adding AI to Core
As "AI Foundations" is set to shape the future of WordPress expandability, it was crucial to carefully clarify the roles of connectors, dashboard settings, and the official AI plugins.
The official documentation notes that AI features are not "forcefully enabled by default." Instead, they are introduced step-by-step via connector settings and optional plugins. For real-world operations where security and control are paramount, this deliberate pace is highly welcome.
Wrap-up: How to Navigate this Major Transition
WordPress 7.0 is a compelling update that redefines the role of a CMS platform in the AI era. However, in the early stages of adoption, site owners should remain prudent regarding API connections and plugin compatibility.
To safely navigate this major transition, we recommend starting with these small steps:
- First, test 7.0 in a staging environment to ensure the new dashboard, command palette, and Font Library do not conflict with your current themes or critical plugins.
- Before enabling AI features, outline your integration strategy and choose which external AI providers (OpenAI, Anthropic, etc.) to connect in the
Connectorssettings. - Plan your editing workflows assuming collaborative editing is not yet present, treating it separately from the future Phase 3 features to avoid immediate operational confusion.