WordPress 7.0 "Armstrong": New Features, AI Integration & What's Still Missing (2026)

WordPress 7.0, codenamed "Armstrong" after jazz legend Louis Armstrong, officially launched on May 20, 2026. It is the most significant release the platform has seen since Gutenberg arrived in 2018. After a turbulent 2025 shaped by legal battles between Automattic and WP Engine, the core team used the extra runway to deliver something genuinely substantial: a native AI framework, the first serious admin redesign in over a decade, Gutenberg Phase 3, new blocks, browser-side media processing, and a modernised developer toolkit.

Part 1: Gutenberg Phase 3 Begins

Phase 1 brought the block editor. Phase 2 brought Full Site Editing. WordPress 7.0 formally kicks off Phase 3, focused on collaboration and team workflows. The headline feature — real-time co-editing — was cut 12 days before launch due to database stability issues, but the infrastructure underneath it shipped. The platform is genuinely more team-ready than before.

WordPress powers over 43% of all websites on the internet. Even incremental improvements to this platform have enormous downstream impact for millions of site owners, developers, and content teams.

Part 2: Native AI Infrastructure

The biggest architectural addition in 7.0. For the first time, WordPress ships with a first-class AI layer in core — not a third-party plugin, not an optional add-on.

WP AI Client

A provider-agnostic interface that lets WordPress communicate with any generative AI model. Think of it as a universal translator between WordPress and AI providers.

Connectors API (Settings › Connectors)

A new admin page where site owners enter API keys once for any supported AI provider. WordPress 7.0 ships with three default connectors: OpenAI, Google Gemini, and Anthropic Claude. Enter your key once — every compatible plugin reads from that single location. No more per-plugin API key setup.

Abilities API

Defines precisely what AI tools are permitted to do inside your WordPress installation. Plugins must explicitly register capabilities (creating posts, editing metadata, generating alt text). AI agents operate strictly within those declared boundaries — a security guardrail around automation.

Workflows API

Supports chained AI tasks and multi-step automation sequences within the editor.

Before WordPress 7.0, every AI plugin reinvented the wheel — separate API key management, separate interfaces, separate security models. The WP AI Client replaces that fragmentation with one standardised infrastructure layer.

Part 3: DataViews — The Rebuilt Admin Dashboard

WordPress's admin interface had not been meaningfully redesigned since 2013. DataViews changes that — a React-based replacement for the classic WP_List_Table system powering Posts, Pages, and Media management screens.

• Zero-reload filtering: Sorting, filtering, and bulk editing happen instantly without full-page reloads
• New layout modes: Activity timeline view and compact list mode for power users
• Modern visual design: Unified design tokens, cleaner typography, consistent spacing
• Inline editing: Edit content properties without leaving the list view
• Custom post type integration: All CPTs now feel native in the modernised interface

Compatibility warning: DataViews is not backward-compatible with custom WP_List_Table implementations. If you have built white-label dashboards using WP_List_Table, those will need rebuilding. Always test on staging before updating production sites.

Part 4: Block-Level Notes and Visual Revisions

Block-level Notes let editors leave comments on specific blocks within a post — not just on the post as a whole. This enables inline feedback loops between writers, editors, and designers without leaving WordPress.

Visual Revisions Screen replaces the old unintuitive revisions system with a graphical history that makes it easy to see what changed between versions and roll back with confidence.

Part 5: Two New Blocks

Breadcrumbs Block: Renders contextual breadcrumb navigation automatically — previously required plugins or manual theme implementation. Ideal for content-heavy sites and WooCommerce stores.

Icons Block: A flexible icon renderer supporting custom SVGs, enabling richer visual layouts without extra plugins or custom code.

Part 6: Client-Side Media Processing

WordPress 7.0 adds browser-side image processing powered by WebAssembly. Images can now be resized, compressed, and converted in the browser before uploading to the server — faster uploads, reduced server load, and better handling of large files on shared hosting environments.

Part 7: PHP-Only Block Registration

Developers can now register blocks using PHP without JavaScript registration. Inspector controls are generated automatically. This dramatically reduces boilerplate code, lowers the barrier for PHP-focused developers, and makes custom block development faster. Block Bindings also gain support for pattern overrides, making it easier to connect blocks with dynamic data sources.

Part 8: Font Library and Responsive Block Visibility

A dedicated Fonts management page under Appearance lets site owners upload, preview, and apply custom fonts across the entire site without plugins. Block themes now support native font management.

Responsive block visibility controls allow editors to show or hide specific blocks on desktop, tablet, or mobile — directly from the editor, without writing CSS. This feature alone eliminates a common plugin dependency for many sites.

Part 9: What Is Still Missing

• Real-time collaboration (postponed): Cut 12 days before launch due to database instability. WordPress 7.1 (August 2026) is the target
• No native AI content generation: The AI infrastructure shipped; features that use it will come from the plugin ecosystem
• Drag-and-drop page building still requires plugins: The core editor still cannot match Elementor or Divi for non-technical users
• WooCommerce remains disconnected from core: No native ecommerce — 6+ million WooCommerce stores get nothing directly from this release for commerce features
• DataViews migration debt: Thousands of plugins and custom admin implementations need rebuilding for compatibility
• No Multisite modernisation: WordPress Multisite remains architecturally clunky compared to modern alternatives
• Performance still plugin-dependent: Image optimisation, code splitting, and advanced caching still rely on tools like WP Rocket and LiteSpeed Cache

Part 10: Should You Update?

Yes — but thoughtfully. Test on staging first. Audit plugins that use WP_List_Table implementations. Verify PHP 7.4+ compatibility on your server. Review AI-capable plugins against the new Abilities API. The Connectors system is opt-in — you do not need an AI provider account to benefit from the other 7.0 improvements.

Conclusion

WordPress 7.0 "Armstrong" is the most important release in years. Real-time collaboration slipped, native ecommerce remains absent, and the AI features are infrastructure rather than end-user tools. But the foundation it lays is significant. The native AI layer standardises a fragmented plugin landscape. DataViews modernises an admin that was truly showing its age. Phase 3 of Gutenberg is underway. WordPress 7.1 will be the real test.