WordPress 7.0 “Armstrong” Is Here: Every New Feature You Need to Know

WordPress 7.0 “Armstrong” is officially here. Released on May 20, 2026, this version is more than a routine update. It introduces a new AI foundation inside WordPress, a refreshed dashboard experience, stronger design tools, new blocks, developer APIs, accessibility improvements, and a clearer path for how WordPress will evolve as a modern content operating system.

The release is named after Louis Armstrong, the legendary jazz musician known for transforming jazz with his unmistakable trumpet, voice, improvisation, and solo style. WordPress describes 7.0 in the same spirit: a release designed to help creators, business owners, agencies, and developers build with their own personal touch.

This guide breaks down every major WordPress 7.0 feature in plain English, explains what matters for site owners, and gives agencies and developers a practical upgrade checklist before moving a production website to Armstrong.

Why WordPress 7.0 Matters

WordPress has been moving from a traditional CMS into a flexible publishing, design, and application platform for years. WordPress 7.0 accelerates that shift.

Earlier major releases focused heavily on the block editor, full-site editing, theme.json, patterns, and reusable design systems. Armstrong adds another layer: AI infrastructure inside WordPress Core, a more modern admin interface, and more precise design controls for teams building serious websites.

For business owners, this means WordPress is becoming easier to manage and more capable without relying on dozens of disconnected plugins. For agencies, it means better tools for faster builds, safer client workflows, and cleaner customization. For developers, it means more standardized APIs for AI, blocks, interactivity, routing, and admin interfaces.

1. AI-Integrated WordPress: The Biggest Strategic Change

The headline feature in WordPress 7.0 is not a single button or a single AI writing tool. It is the foundation that allows WordPress, plugins, and future workflows to interact with generative AI models in a more standardized way.

WordPress 7.0 introduces the WP AI Client, a provider-agnostic interface that lets compatible plugins communicate with generative AI models without every plugin needing to build its own separate connection system.

In simple terms, instead of every AI plugin asking users to paste separate API keys into separate settings pages, WordPress is moving toward a central connection layer. That creates a more scalable foundation for AI-powered publishing, automation, media generation, content assistance, and workflow tools.

What the WP AI Client Does

• Provides a central interface for AI model communication.
• Works with the new Connectors foundation for managing external AI connections.
• Allows developers to build AI-powered features without locking users into one provider.
• Supports model preference and capability detection, so tools can choose the best available model for a task.
• Connects with the Abilities API to support more advanced workflows.

This matters because WordPress is not trying to become only an AI content writer. It is creating a foundation where AI can be integrated into publishing, editing, media, accessibility, site management, automation, and future agent-style workflows.

What Site Owners Should Know

The AI foundation does not mean every website suddenly starts using AI automatically. A site still needs configured connectors, compatible plugins, and intentional workflows. For businesses, the smart approach is to use AI where it improves operations: draft support, image assistance, alt text suggestions, content structure, internal linking ideas, product content workflows, and editorial speed.

For agencies, this is a major opportunity. WordPress AI implementation can become a serious service line: configuring secure AI workflows, connecting approved providers, creating brand-safe prompts, and building AI-assisted editorial systems for clients.

2. Connectors Screen: One Place to Manage External Connections

WordPress 7.0 adds a dedicated Connectors area for managing external connections. This is important because AI and automation features often need secure access to outside services, such as model providers or other APIs.

Instead of burying these settings across different plugins, Armstrong introduces a more centralized approach. This makes the admin experience cleaner and gives developers a common pattern for building integrations.

For a business website, this could eventually reduce operational complexity. A marketing team should not need to hunt through ten plugin settings pages just to understand which services are connected. A central connector model improves visibility, security, and long-term maintainability.

3. Client-Side Abilities API and Command-Based Workflows

WordPress 7.0 expands the Abilities API with a JavaScript counterpart called the Client-Side Abilities package. This gives developers a way to expose and organize actions that can be discovered and used inside user interfaces, including command-palette style experiences.

Think of abilities as structured actions WordPress can understand. A plugin can describe what it can do, and a UI or AI-assisted workflow can discover those actions more intelligently.

For example, future workflows could combine actions like:

• Generate a draft outline.
• Create SEO metadata.
• Suggest image alt text.
• Check missing schema.
• Publish or schedule content after review.

That does not mean every workflow is automatic today. It means WordPress 7.0 creates the technical foundation for smarter, more connected workflows tomorrow.

4. A Modernized WordPress Dashboard

The WordPress admin area has carried years of legacy design decisions. WordPress 7.0 starts modernizing that experience with a refreshed admin theme, smoother transitions, and more intuitive navigation.

The new dashboard direction includes a cleaner visual style, modern color treatment, smoother movement between admin screens, and a more polished user experience across wp-admin.

View Transitions in WP Admin

WordPress 7.0 introduces view transitions in wp-admin, creating a smoother feeling when users move between dashboard screens. Importantly, these transitions respect reduced-motion preferences at the operating system level, which helps preserve accessibility for users who prefer less motion.

Command Palette Shortcut

The new Command Palette shortcut is one of the most practical admin improvements. A ⌘K or Ctrl+K shortcut appears in the upper admin bar, making it faster to access editing tools, settings, and actions from anywhere in the dashboard.

For site managers and agencies, this can reduce friction. Instead of clicking through multiple menus, users can jump directly to the thing they need.

5. Dedicated Font Library Page

WordPress 7.0 expands the Font Library with a dedicated font management page. Fonts can now be managed, uploaded, and installed from one place across block, hybrid, and classic themes.

This is valuable for businesses because typography is a core brand asset. A dedicated font page makes it easier to maintain brand consistency without relying entirely on page builder settings or custom theme code.

For agencies, this also simplifies client training. A client can manage approved fonts from a clearer location instead of editing theme files, adding custom CSS, or installing extra font plugins.

6. Visual Revisions: Easier Content Review

WordPress has had revisions for a long time, but comparing changes has often felt technical and text-heavy. WordPress 7.0 introduces Visual Revisions, which make it easier to compare changes directly in the editor.

Users can compare versions with a visual slider, review a summary of changes, and understand what changed without reading raw revision text.

This is especially useful for:

• Editorial teams reviewing copy changes.
• Agencies managing client approvals.
• Businesses with multiple users editing the same page.
• Content teams trying to restore a previous version safely.

For high-value pages like homepages, landing pages, service pages, and WooCommerce product pages, visual revisions can reduce mistakes and make rollback decisions easier.

7. Improved Iframed Editor Stability

WordPress 7.0 improves the iframed editor experience. When all inserted blocks use Block API version 3 or higher, the post editor can be loaded inside an iframe for a more stable and isolated editing environment.

This matters because editor styling conflicts are one of the common issues on complex WordPress websites. A better isolated editor experience helps reduce interference from admin styles, plugin CSS, and theme behavior.

For older blocks, WordPress keeps backwards compatibility by removing the iframe where needed. That is important for real-world sites that rely on older plugins or custom blocks.

8. New Blocks: Heading, Breadcrumbs, Icons, and More

WordPress 7.0 adds and improves several blocks that make the editor more practical for building complete pages without extra plugins.

New Heading Block

The new Heading block includes variations for heading levels, quick transforms, and better discoverability through search and slash commands. This helps editors structure content more clearly and improve on-page SEO.

New Breadcrumbs Block

The Breadcrumbs block automatically reflects a site’s navigational hierarchy. It can be used in site parts like headers and gives developers filters to modify breadcrumb trails.

This is a strong SEO and UX addition. Breadcrumbs help users understand where they are on a site, and they help search engines understand page hierarchy.

New Icons Block

The Icons block gives users a cleaner way to add visual signals inside layouts without relying on third-party icon plugins for basic design needs.

Gallery Lightbox Slideshow

The Gallery block now supports lightbox behavior with a slideshow option. This is useful for portfolios, case studies, product galleries, media-heavy pages, and visual storytelling.

Video as a Cover Block Background

WordPress 7.0 adds support for video embeds as section backgrounds in the Cover block. This gives designers more flexibility for hero sections, campaign pages, and landing pages without fully custom development.

9. Responsive Block Visibility by Device

One of the most practical design updates is responsive block visibility. Editors can hide or reveal individual blocks based on device type without changing other viewports.

This is useful when a desktop section is too complex for mobile, when a mobile CTA needs to be shorter, or when layout differences are required for conversion optimization.

Used carefully, device visibility can improve mobile UX and page conversion. Used poorly, it can create duplicate content, bloated pages, and maintenance issues. The best approach is to use responsive visibility for strategic differences, not as a shortcut for fixing broken layouts.

10. Custom Navigation Overlays for Mobile

Mobile navigation gets a meaningful upgrade in WordPress 7.0. Hamburger menu overlays can now be designed with blocks and patterns inside the Site Editor.

There is also a dedicated Navigation Overlay Close block, which gives theme authors and site editors more control over how the mobile menu opens, looks, and closes.

For brands, this makes the mobile navigation experience more customizable. For agencies, it reduces the need for custom-coded menu overlays in many projects.

11. Pattern Editing and Pattern Overrides

Patterns continue to become more powerful. WordPress 7.0 improves pattern-level editing and expands pattern overrides, including support for custom blocks through block bindings.

This matters for scalable site building. Agencies can create structured design systems where clients can safely edit specific content areas without breaking layout logic.

For example, a service card pattern might allow the client to edit the title, short description, and CTA, while preserving the layout, spacing, and style. That is exactly the kind of controlled editing that professional WordPress builds need.

12. Block-Level Custom CSS

WordPress 7.0 introduces custom CSS at the individual block level. This gives editors and advanced users more precise control without forcing every small adjustment into a theme stylesheet.

This is powerful, but it should be used carefully. For client sites, agencies should still prefer reusable global styles, theme.json settings, and design tokens wherever possible. Block-level CSS is best for tactical exceptions, campaign pages, and controlled customizations.

13. Better Typography and Dimensions Controls

WordPress 7.0 adds more block support for typography and layout control, including text indent support, text column support for paragraphs, width and height support, dimension presets, and aspect ratio support for wide and full images.

These upgrades help WordPress compete more strongly with visual builders while keeping design controls closer to Core.

For content-heavy businesses, the paragraph text columns and typography controls can improve editorial layouts. For agencies, dimension presets make it easier to enforce consistent spacing and sizing across blocks.

14. PHP-Only Block Registration

For developers, PHP-only block registration is one of the most important WordPress 7.0 changes.

Developers can create blocks and patterns on the server using PHP and register them with the Block API. Auto-registration makes it easier to expose server-created blocks to the editor, and automatic inspector controls can be generated from attributes.

This reduces the amount of JavaScript required for certain types of blocks and can speed up development for agencies that build custom blocks for client sites.

15. Interactivity API Improvements

The Interactivity API continues to mature. WordPress 7.0 adds a new watch() function to the @wordpress/interactivity package, allowing callbacks to re-run when accessed signals change.

This helps developers build more reactive front-end experiences using WordPress-native patterns instead of reaching immediately for heavy frameworks or unrelated JavaScript architecture.

16. DataViews and DataForms Improvements

WordPress 7.0 improves DataViews and DataForms with new layouts, better modal appearance, and support for registering third-party field types in the Field API.

This matters because the WordPress admin experience is gradually moving toward more flexible, app-like data management. Plugin developers can build cleaner interfaces for managing content, settings, workflows, and custom data.

17. Site Editor Routing and Extensibility

Armstrong lays the foundation for a more extensible Site Editor. It introduces routing, route validation, and a new @wordpress/boot package that allows plugins to build custom Site Editor pages.

This is not the most visible change for everyday users, but it is strategically important. It means plugin authors can build more integrated editing experiences inside the WordPress design environment instead of sending users to disconnected custom admin pages.

18. Security and User Role Improvements

WordPress 7.0 improves default user-role safety by removing Administrator and Editor roles from the new user default selector under General settings.

That is a smart security move. Many site breaches and client-side mistakes happen because users are given higher access than they need. By reducing the chance of setting overly powerful roles as default, WordPress makes accidental privilege escalation less likely.

Site Health can also alert if one of those roles had been selected before updating, and developers get a filter to adjust excluded default roles when needed.

19. Accessibility Improvements

WordPress 7.0 includes several accessibility improvements that matter for both compliance and real usability.

• Password reset now pre-populates the username to better align with WCAG 2.2 expectations.
• A new wp_get_image_alttext() function can import image alt text metadata from IPTC data.
• View transitions respect reduced-motion preferences.
• Title attributes can be removed from selected functions, and some author link functions remove them by default.
• Hidden screen-reader text handling has been improved so assistive technology does not read content letter by letter.

These changes support a more accessible editing and browsing experience. For business websites, accessibility is not only about compliance. It improves usability, reach, and trust.

20. PHP 7.4 Minimum Requirement

One of the most important technical notes: WordPress Core’s minimum PHP version is now PHP 7.4.

If your hosting environment still runs an older PHP version, you should not update blindly. Check your hosting panel, staging site, theme, and plugins before upgrading.

For best performance and long-term compatibility, most serious production sites should be planning for a modern PHP 8.x environment. PHP 7.4 is the minimum floor, not the performance target.

WordPress 7.0 Upgrade Checklist

Before updating a live website to WordPress 7.0, follow a proper upgrade process. This is especially important for WooCommerce stores, membership sites, LMS platforms, high-traffic blogs, SaaS marketing sites, and agency-managed client websites.

1. Create a Full Backup

Back up the full database and files before updating. Do not rely only on your host’s automatic backup unless you have tested restore access.

2. Test on Staging First

Clone the website to staging and update WordPress there first. Check the homepage, top landing pages, checkout flow, forms, search, menus, dashboards, custom post types, and key plugins.

3. Check PHP Version

Confirm your server is running PHP 7.4 or higher. For performance, use a supported modern PHP 8.x version where your plugins and theme are compatible.

4. Audit Critical Plugins

Pay extra attention to plugins that touch the editor, custom blocks, AI tools, SEO metadata, WooCommerce templates, multilingual content, forms, caching, security, and user roles.

5. Test the Editor

Create and edit a post, page, reusable pattern, navigation area, and any custom block used by the site. Confirm the editor loads cleanly and does not show console errors.

6. Review Design and Mobile Layouts

Because WordPress 7.0 adds new responsive controls, check mobile and tablet layouts carefully. Make sure visibility settings are not hiding important CTAs or SEO-critical content.

7. Re-Test Performance

Run performance checks after the update. Confirm caching still works, Core Web Vitals remain healthy, and no new JavaScript or CSS conflicts were introduced.

Who Should Update Immediately?

You can consider updating quickly if your site is simple, uses well-maintained themes and plugins, has PHP 7.4+ already active, and you have staging plus backups ready.

Examples:

• Small brochure websites.
• Blogs using mostly Core blocks.
• Modern block themes with minimal plugin dependency.
• Development sites or new builds not yet live.

Who Should Wait and Test More Carefully?

You should be more cautious if your site has revenue-critical functionality or complex plugin dependencies.

Examples:

• WooCommerce stores with custom checkout logic.
• Membership and LMS websites.
• Websites using many custom blocks or page builders.
• Multilingual sites.
• High-traffic lead generation websites.
• Websites with custom user roles and permissions.
• Sites using advanced caching, CDN, or custom server rules.

For these sites, test first. The cost of a broken checkout, broken lead form, or broken editor is much higher than waiting a few days to validate compatibility.

What WordPress 7.0 Means for Agencies

For WordPress agencies, Armstrong is a major opportunity. Clients are going to ask about AI, automation, accessibility, performance, and modernization. WordPress 7.0 gives agencies a stronger foundation to package those services.

High-value services around this release include:

• WordPress 7.0 upgrade audits.
• PHP and hosting compatibility reviews.
• AI connector setup and governance.
• Brand-safe AI content workflows.
• Editor cleanup and block modernization.
• Navigation and mobile UX improvements.
• Accessibility fixes and alt text workflows.
• Custom block development using PHP-only registration.
• Theme.json design system cleanup.
• WooCommerce compatibility testing.

What WordPress 7.0 Means for Business Owners

If you own a business website, the key takeaway is simple: WordPress is becoming more powerful, but also more strategic.

You should not treat this as just another “click update” release. It introduces new foundations that affect AI, admin workflows, editor behavior, design systems, PHP requirements, accessibility, and developer APIs.

The best way to benefit from WordPress 7.0 is to use it as a chance to clean up your site:

• Remove abandoned plugins.
• Update your theme and child theme.
• Check PHP and server health.
• Improve page speed.
• Fix missing image alt text.
• Review schema and SEO metadata.
• Modernize important service pages.
• Build safer AI-assisted content workflows.

WordPress 7.0 FAQ

Is WordPress 7.0 officially released?

Yes. WordPress 7.0 “Armstrong” was released to the public on May 20, 2026.

Why is it called Armstrong?

WordPress major releases are named after musicians. Version 7.0 honors Louis Armstrong, one of the most influential jazz musicians of all time.

What is the biggest new feature in WordPress 7.0?

The biggest strategic feature is the AI foundation: WP AI Client, Connectors, and Abilities API improvements. These create a more standardized way for WordPress and plugins to work with AI models and workflows.

Does WordPress 7.0 include new blocks?

Yes. WordPress 7.0 includes new and improved blocks such as Heading, Breadcrumbs, Icons, Gallery lightbox slideshow support, and video embed support inside the Cover block.

What PHP version does WordPress 7.0 require?

WordPress Core’s minimum PHP version is now PHP 7.4. Site owners should check hosting compatibility before updating.

Should WooCommerce stores update immediately?

WooCommerce stores should test on staging first. Confirm checkout, payment gateways, product pages, cart behavior, emails, subscriptions, shipping logic, and analytics before updating the live store.

Does WordPress 7.0 replace page builders?

No. Page builders still have their place. But WordPress 7.0 continues improving Core design tools, blocks, responsive controls, patterns, and editor capabilities, which reduces dependency on heavy builders for many simpler layouts.

Final Verdict: WordPress 7.0 Is a Foundation Release

WordPress 7.0 “Armstrong” is not just a cosmetic release. It is a foundation release.

The AI Client, Connectors, and Abilities API point toward a future where WordPress workflows become more intelligent and connected. The modern dashboard, Command Palette, Font Library, and Visual Revisions make day-to-day site management easier. The new blocks and responsive controls improve page building. Developer upgrades like PHP-only block registration, Interactivity API improvements, and Site Editor routing make WordPress more extensible.

For site owners, the recommendation is clear: do not ignore WordPress 7.0, but do not update carelessly either. Back up, test on staging, check PHP, review plugin compatibility, and use the release as an opportunity to modernize your website.

Official WordPress 7.0 Resources

• Official WordPress 7.0 “Armstrong” release announcement
• WordPress 7.0 release notes
• WordPress 7.0 Field Guide for developers
• WordPress release archive