What’s New in WordPress® 7.0? A Community Member’s Perspective

I’ve been designing and building on WordPress^®[1] since 2006. In those two decades, I’ve watched it evolve from a simple blogging tool into the most powerful content management tool on the open web. Yet, for many of us, that journey has felt like a series of compromises. 

Developing great experiences often became a tug-of-war between the creative vision and the software’s technical limitations, as we fought with custom CSS for mobile menus or installed a dozen third-party plugins just to add a breadcrumb trail. These friction points don’t just slow down the workflow; they add weight to our databases and complexity to our maintenance.

On May 20, 2026, WordPress 7.0, aka Armstrong, officially moved WordPress CMS users past these limitations and into what I believe is a better, more future-ready state. The release has turned the core software into a more sophisticated, design-focused operating system and set the stage for the next phase of the web with a native AI framework built in.

Here is how WordPress 7.0 is improving collaborative workflows, modernizing core functionality, and preparing itself for the intelligent web.

Standardizing AI integration for future readiness

Historically, every plugin with AI features required its own independent setup. If you used multiple AI-powered tools, you had to manage several different connections and API keys.

WordPress 7.0 addresses this with a shared infrastructure layer through two new features (built on top of the Abilities API from 6.9): the Connectors API and the WP AI Client SDK. Together, they provide a standardized infrastructure for connecting WordPress websites to external AI providers like OpenAI, Google, and Anthropic. 

The Connectors API is a new framework for managing external service connections. While it currently focuses on AI providers, its architecture is designed to support other external services in the future.

The WP AI Client SDK is a WordPress-native library (wordpress/wp-ai-client) that allows developers to interact with multiple AI providers through a single, consistent interface. It uses the WordPress HTTP API under the hood and integrates seamlessly with the Abilities API to expose WordPress-specific functions to AI models.

These features are some of the first major steps toward AI integration, allowing developers to interact and connect with AI-powered features in a secure, consistent, and easy-to-configure way. 

Design flexibility with safety rails

One of the most persistent frustrations for designers has been the lack of native control over the mobile hamburger menu. In 7.0, navigation overlays have finally become fully customizable template parts. Mike McAllister’s work with the Ollie Menu Designer was a clear inspiration for this feature. He proved that the block editor could handle complex menus if the core software provided the right framework.

Users can now design exactly what happens when a visitor clicks a mobile menu, incorporating social icons, a search bar, or a contact form. Native navigation overlays mark the end of fighting with theme CSS or installing heavy third-party menu plugins, and any images in the navigation overlay are automatically deprioritized to protect the page’s critical rendering path.

Outside the navigation menu, expanded Pattern Editing capabilities, specifically “content-only” mode, allow users to better protect their design patterns. For example, if a designer builds a complex hero section as a pattern and another user goes in to edit images, copy, or links, the block structure and styling will be visible but uneditable by default. Your protected patterns now act as individual blocks in their own right, and users can click “edit pattern” for greater editing access to all available elements. Decoupling content elements from structural elements will help prevent accidental breakage of design elements during routine site updates.

Core performance and modernization

Core updates in 7.0 focused on long-term stability and hardening the codebase. The release includes a refreshed admin experience, optimized core code, more efficient database handling, and expanded native block functionality to reduce reliance on plugins.

As we mentioned above, improved accuracy in prioritizing image loading prevents hidden images in navigation overlays or interactive blocks from degrading the loading of critical resources. In classic themes, on-demand block stylesheet loading is more reliable, and classic scripts can now list script modules as dependencies to reduce render-blocking.

Version 7.0 also raises the minimum PHP version requirement to 7.4, allowing core to leverage newer features in the language. 

Each of these enhancements (and more we haven’t discussed here!) improves the out-of-the-box performance of the WordPress core software.

Improving native functionality through blocks

For years, WordPress development relied on a lean core software package supplemented by lots of plugins to piecemeal essential functionality. WordPress 7.0 introduces more blocks and expands functionality for some existing blocks so they can handle tasks previously outsourced to third-party code, allowing core to do more.

The Grid block is now responsive across columns, enabling multi-column layouts that reflow perfectly across devices. It’s a modern layout tool developers have been waiting for.

The addition of Breadcrumbs and Icon blocks is another welcome expansion. The Breadcrumbs block is highly customizable and schema-ready out of the box, and the Icon block supports scalable SVGs with 88 preloaded icons, all ready to use without requiring massive font libraries.

The Gallery block now supports lightbox navigation, so users can finally browse through image sets using on-screen buttons or keyboard arrows. The system automatically skips any images where the lightbox is disabled to provide a seamless experience.

A few additional blocks have also been refined:

• Query Loop block: Faster and more reliable data fetching.
• Heading block: Updated variations for better control over H1-H6 hierarchy.
• Paragraph block: Text columns and text indent support.

New viewport-based block visibility lets users hide any block based on the viewer’s device type. No plugin or custom CSS code required; simply choose which blocks you want to hide and on what device type. In List View, blocks will display an icon indicating certain viewports are hidden, and hovering over the icon shows which viewports those are.

Users can also register blocks entirely with PHP, which will be a welcome change for those who miss the simplicity of shortcodes. 

These core and block improvements provide a solid structural foundation, but 7.0 goes even further by giving designers guardrails to ensure their layouts remain intact during the editing process.

WP Engine’s full-time contribution team

WP Engine’s sponsored contributors, Weston Ruter, John Parris, and Joe Fusco, were instrumental in building and testing many of the features included in WordPress 7.0. 

Both Fusco and Parris concentrated on the real-time collaboration (RTC) framework, which was tabled for 7.0 but will likely ship with a future release. Fusco spearheaded the migration of collaboration data from post meta to dedicated database tables, ensuring the system remains performant and scalable, while Parris optimized RTC by implementing awareness-state caching and refining REST endpoints to eliminate race conditions and ensure multi-user editing feels instantaneous and reliable. 

Ruter’s contributions focused primarily on core modernization and performance optimization. He led the integration of advanced static analysis tools like PHPStan to harden the codebase, helped bring the command palette to mobile, contributed to smooth admin view transitions, and brought the built-in code editor up to date. His extensive work on the script/style dependency system is crucial for maintaining CSS cascade integrity in classic themes, and he led key media optimizations, including fine-tuning fetchpriority for images.

Along with dozens of other community members, WP Engine’s core contributor team has done the prep work for a new, collaborative experience in a future WordPress release and reinforced the underlying stability and speed of the world’s most-used CMS in time for 7.0.

Looking ahead to 2026

While WordPress 7.0 is the landmark release of the year, it is only the beginning of the 2026 roadmap. We are looking forward to even more exciting updates in version 7.1 (expected in August) and 7.2 (expected in December).

WordPress 7.0 is making a major leap into a more collaborative, AI-ready system. Our gratitude goes out to the entire community of contributors who made this release possible, and special thanks to WP Engine’s sponsored core contribution team for all their hard work on 7.0.

1 WP Engine is a proud member and supporter of the community of WordPress® users. The WordPress® trademarks are the intellectual property of the WordPress Foundation, and the Woo® and WooCommerce® trademarks are the intellectual property of WooCommerce, Inc. Uses of the WordPress®, Woo®, and WooCommerce® names in this website are for identification purposes only and do not imply an endorsement by WordPress Foundation or WooCommerce, Inc. WP Engine is not endorsed or owned by, or affiliated with, the WordPress Foundation or WooCommerce, Inc.