WordPress 7.0 feels less like a routine update and more like a statement about where the project wants to go next. It’s a major shift in priorities: collaboration, AI integration, and more visual editing experiences. Some changes are clearly aimed at enterprises and newsrooms, others at developers, and a few at everyday site owners.
Release date: May 20, 2026.
Real-time collaboration (RTC)
The headline feature is real-time collaboration. You can now edit a post or page with someone else and see their changes as they happen — similar to Google Docs. Under the hood it uses CRDTs (conflict‑free replicated data types) to resolve edits and relies on HTTP polling so it works across a wide range of hosts.
Key limits and details:
– Initially limited to two simultaneous collaborators to reduce host strain.
– Hosts can replace the transport/storage layer; developers can tweak polling via JS filters.
– RTC is disabled when metaboxes are present, nudging plugin authors to rethink integrations.
– After some community pushback, real‑time editing is opt‑in rather than on by default.
Who should care? This is exciting for teams, editorial rooms, and enterprise sites that need live coediting. For solo writers or small teams it’ll feel unnecessary (or even intrusive) at first. The feature is early-stage, though, and likely to evolve.
AI foundation: Connectors API and wp_ai_client
Instead of shipping lots of opinionated AI features, WordPress 7.0 provides the plumbing so plugins and themes can add AI easily and safely.
What’s included:
– A new Connectors screen in wp-admin for managing API keys (OpenAI, Anthropic, Google, etc.).
– A Connectors API for plugins that need external credentials (not limited to AI).
– A provider-agnostic PHP helper (wp_ai_client_prompt()) that sends prompts to whatever LLM provider the site is configured to use.
Why this matters: WordPress is positioning itself as a neutral orchestration layer. The core handles credential storage and basic prompting; third-party developers build the user experiences. That’s a pragmatic approach that helps developers avoid reinventing credential management while keeping WordPress vendor-agnostic.
Visual revisions
Revisions are now integrated into the main editor with a visual timeline slider, color-coded changes (yellow = modified, red = deleted, green = added), a minimap on the scrollbar showing where edits occur, and a Restore button when you browse history.
Pros: More approachable for non-developers and quicker to access.
Cons: You lose some power-user features from the old revisions screen: you don’t see the raw HTML/source, and you can’t compare any two arbitrary revisions — only a chosen past version against the one immediately before it.
Developer highlights
PHP-only block registration: You can register blocks with only PHP (no JS build step) using register_block_type with an autoRegister flag and a render_callback. That makes simple server-rendered blocks much easier to build and maintain.
Pattern overrides for custom blocks: Pattern overrides now work for any block that supports Block Bindings, not just a few core blocks. That’s big for agencies and developers who use custom blocks in templated patterns.
Client-side Abilities API: The JavaScript side of the Abilities API arrives as @wordpress/abilities (state-only) and @wordpress/core-abilities (REST-connected). The docs hint at future use cases for browser agents, extensions, and interoperability with AI agents.
Custom CSS per block instance: A CSS input in the block sidebar lets editors add declarations (no selector needed). Use & for nesting. This fills a long-standing gap for per-instance styling without custom classes.
Design and content-editing wins
Navigation overlays: More control over mobile hamburger menus, including built-in overlay patterns, an “always visible” submenu toggle, and the ability to create pages from the Navigation block.
Content-focused pattern editing: Patterns default to a content-only editing mode that presents clean, editable text/image fields in the sidebar while preserving layout. You can detach if you need full block access — useful when handing sites over to clients.
Viewport-based block visibility: Toggle block visibility per device (desktop, tablet, mobile) from the toolbar. What used to require a plugin is now native.
Command Palette reminder
WordPress has a Command Palette available from anywhere with ⌘K / Ctrl+K. It’s a quick way to jump to settings, search, and actions without hunting through menus.
Verdict
Overall this is a strong, forward-looking release. Not every feature will excite every user, but the themes are clear: collaboration, adaptable AI integration, and more approachable editing tools. The RTC rollout is cautious (and opinionated), but understandable given hosting constraints. The AI connectors are the most strategically important addition — they make it much easier for the ecosystem to build diverse AI experiences without centralizing on a single provider.
If you’re a developer, the new APIs and PHP-only blocks reduce friction for building features. If you manage content teams or newsrooms, RTC and visual revisions could change workflows. If you’re a solo blogger, the most tangible wins are probably the visual revisions, block CSS, and device visibility controls.
Kudos to the contributors for a thoughtful release. What do you think? Which feature are you most curious to try?
Want to speed up your WordPress site? Join our short crash course on practical optimizations and learn how to cut load times dramatically. Enter your email on our site to subscribe to a weekly newsletter and get the course details — you can unsubscribe anytime.