WordPress 7.0, codenamed “Armstrong”, landed on 20 May 2026, and it is one of the most significant releases in years. The big story is not a new block or a faster editor, though you get plenty of both. It is that WordPress now ships with a native, provider-agnostic AI foundation built straight into the core, alongside a refreshed admin and a batch of design tools that give editors more control without touching code. Here is what shipped in 7.0, and what it means for the sites we build and look after.
A native AI foundation in the core
Until now, using AI in WordPress has meant working around a brittle, fragmented setup. Every AI-powered plugin brought its own configuration and its own way of talking to providers like OpenAI, Anthropic or Google, so running more than one meant juggling separate connections, with little shared visibility into what each was doing behind the scenes. WordPress 7.0 replaces that with a single, shared foundation.
At the centre is the new WP AI Client, which gives plugins one consistent way to talk to generative AI models while WordPress handles the routing behind the scenes. Connections are managed from a new Connectors screen under Settings, which ships with Anthropic, Google and OpenAI ready to configure, and lets you add others. Because the layer is provider-agnostic, a developer can state a preference for which model to use and let WordPress match the right one to the task.
None of this is switched on by default. AI is an opt-in capability you control, which is exactly how it should be treated on a live site. Our standard approach is to test it in staging, agree what is approved, then introduce it to production deliberately rather than all at once.
Alongside that, we are looking into additional solutions, in conversation with both core and plugin developers, that tighten the security and visibility of AI use in WordPress. The aim is straightforward: our clients should be able to explore what AI can do for them and feel confident it is happening safely.
What this opens up for our clients
For content and CMS clients, a connected site can take on the small jobs that quietly eat a content team’s week. That covers drafting and tightening copy, generating sensible alt text for accessibility, summarising long posts, or suggesting topic ideas and angles to write about for SEO based on what is already on the site.
For WooCommerce clients, the same foundation reaches into the store. You can ask for a read on what is selling right now, surface products that are slipping, draft product descriptions that follow your tone, or get a quick summary of recent orders without building a custom report for every question.
Working on your site from Claude Desktop
Your site becomes something you can have a conversation with, and act on, from outside the dashboard
This is where it gets interesting. Building on the same abilities that 7.0 standardises, an MCP adapter lets you connect your WordPress or WooCommerce site to tools like Claude Desktop. Instead of logging into the admin for every small task, you can ask from the AI tool you already have open: pull this month’s best-selling products, suggest five SEO topics based on our existing content, or update a page and push the change back to the site.
Your site becomes something you can have a conversation with, and act on, from outside the dashboard. We can set this up for clients who want it, scoped carefully so the right people have the right level of access.
What we are exploring for Qala
We are particularly excited about what this means for Qala clients. One thing we are looking into is using the AI foundation to make Qala easier to learn and use without leaving your own site admin. Picture asking how to build a particular layout, or how a Qala block works, and getting a clear answer in context, without waiting on a reply to a support question or scrubbing back and forth through a recorded walkthrough to find the part you need. It is early, and we will share more as it takes shape, but the groundwork that 7.0 lays is exactly what makes it possible.
A modernised admin
The dashboard has had its biggest visual refresh in over a decade.
A fresh look, with an easy way out
WordPress 7.0 introduces a new default admin theme called “Modern”, with higher contrast, updated typography and smooth transitions as you move between screens. Not everyone will love a new look on day one, and that is fine. If the new palette is not to your taste, you can switch to a different colour scheme from your own profile page, so each person on your team can set the admin up the way they prefer.
The command palette, a power tool most people have not noticed
One of the quietest but most useful additions is a command palette. Press ⌘K on Mac or Ctrl+K on Windows from anywhere in the admin and a search box opens that lets you jump to screens and run actions without hunting through menus. Anyone used to tools like Slack or VS Code will feel at home immediately. Most WordPress users have no idea it now exists, and it is the kind of thing that quietly saves minutes every day once it becomes a habit.
Visual revisions, revision history people can actually read
WordPress has always kept revisions, but comparing them has meant staring at a technical, line-by-line view that few non-developers enjoy. WordPress 7.0 reworks this into a visual comparison. You can slide between two versions of a page or post, see at a glance what changed and where, and jump straight to that spot on the page.
For any client who regularly reviews changes, an editor checking what a colleague altered, or a team keeping an eye on a busy page, this turns revisions from a developer tool into something a person can read at a glance. It is a small change that removes a regular source of friction.
More design control, less code
The release hands editors and designers more control over the look of a page without dropping into a template or a stylesheet.
Custom CSS, now per block
WordPress 7.0 lets you apply custom CSS to an individual block. This is something our Qala clients have had for a while through Qala’s own tools, so the capability is not new to them. What changes is the source. For the power users among our clients who already work this way, we will adapt gracefully to the version WordPress now provides, so everyone is working to the same standard going forward.
Show the right content on the right device
A favourite of ours from this release is device-based block visibility. You can now show or hide individual blocks depending on whether a visitor is on a desktop, tablet or phone, and you can adjust the breakpoints that decide which is which. That means tailoring what people actually see to the device in their hand, a compact call to action on mobile and a richer layout on desktop, without maintaining two separate pages.
Mobile navigation, and why Qala goes further
7.0 also lets you build and style custom mobile navigation overlays from blocks and patterns, with proper control over the menu that appears behind the hamburger icon. It is a welcome addition to core.
For Qala users it is less of a headline, because we have something more powerful on the way. We are currently beta testing a new feature plugin called Qala Menus with a small group of customers. It goes well beyond a tidy mobile menu, delivering a robust megamenu solution and an entirely new admin interface that stays friendly to use even when a menu structure grows large and complex. If you run a big catalogue or a deep site, this is built for you.
New blocks: Breadcrumbs and Icons
WordPress 7.0 adds a few new blocks, two of which are relevant to how we build. There is a new Breadcrumbs block that reflects a site’s structure automatically, and we are looking at how it fits alongside the breadcrumbs feature Qala already provides. There is also an Icons block, which is a nice complement to our own. The two will likely merge in time, but not in this version: the core block does not yet let you register your own icons, which is something our clients rely on, so for now the two live side by side.
What about real-time collaboration?
If you followed the run-up to 7.0, you may have expected real-time collaboration to be the headline. Google-Docs-style co-editing, several people in the same post at once, live cursors, and an end to the “someone else is editing this” lock. It was meant to be the centrepiece, marking the collaboration milestone on Gutenberg’s long-term roadmap. It did not ship.
the surface area, race conditions, server load, memory efficiency, and the bugs that keep popping up in fuzz tests / etc don’t give me a lot of confidence on our current approach being the robust one we want to support
Matt Mullenweg in the “Making WordPress” Slack
The reason is worth understanding, because it reflects well on the project. Early versions leaned heavily on post metadata and constant background syncing, which created real performance overhead and interfered with how WordPress caches content. The proper fix needs a dedicated database table, and getting that storage design wrong now, only to change it later, would force risky data migrations on every site that had switched the feature on. In early May, WordPress co-founder Matt Mullenweg made the call to pull it, saying he was not confident the current approach was robust enough for core given the surface area, race conditions, server load and bugs still surfacing in testing. The community reaction was largely relief. A delayed feature is better than a fragile one running on a large share of the web.
The good news is simple: it is delayed, not cancelled. Real-time collaboration is back on the roadmap for the next release, WordPress 7.1, currently expected later in 2026. It is also the kind of feature that divides opinion. Editorial teams with several authors working the same content will love it, while clients with a single editor may never feel the need. When it does arrive, we will help you decide whether it earns a place in your workflow rather than turning it on for its own sake.
Under the hood
There is plenty here for developers too. WordPress 7.0 adds PHP-only block registration, so blocks and patterns can be created on the server without a JavaScript build step. The DataViews and DataForms components that power the modern admin gain new layouts and the ability to register custom field types, and the Interactivity API picks up new tools for reacting to changes on the page. If that sounds abstract, it is the same modern foundation our new Qala Menus plugin is built on, so we are already working with these tools hands-on.
Accessibility gets real attention as well, with fixes that bring the login and password-reset flow in line with WCAG 2.2, alt text that can be pulled automatically from an image’s IPTC metadata, and view transitions that respect a visitor’s reduced-motion preference.
One practical note for anyone planning an upgrade: the minimum PHP version is now 7.4. Our clients are already on PHP 8, comfortably clear of that floor. We follow PHP versioning and WordPress support closely so our server software stays current without ever sitting on the bleeding edge, because stability always comes first.
Getting your site ready
A release this significant is only good news if your site is ready for it. Rather than rushing 7.0 onto client sites the moment it landed, we have taken the time to put it through its paces across the stack our clients rely on, and to confirm Qala, our packaged WordPress and WooCommerce solution, is fully compatible with the new core, from the modernised admin to the AI foundation. For our WooCommerce clients in particular, we test against real-world, high-traffic stores so nothing surprises anyone at the checkout. Stability for our clients comes before being first to the new thing.
So when you are ready to take advantage of 7.0, the groundwork is in place, handled the careful way we handle everything.
Ready to make the most of WordPress 7.0?
We can help you put the new AI tools to work and upgrade with confidence.