WordPress 7.0 marks a clear change in direction — not just another incremental update, but a set of features that reshapes what WordPress wants to be. It’s aiming for collaboration-first workflows, a neutral AI integration layer, and cleaner editing tools. Here’s what matters and why.
Release date
Planned release: May 20, 2026.
Top new features and what they mean
1) Real-time collaboration (RTC)
– What it is: Live, multiuser editing for posts and pages. You’ll see others’ edits as they happen, much like Google Docs.
– How it works: CRDTs (Conflict-free Replicated Data Types) for resolving conflicts; built on HTTP polling so it works across hosts; hosts can swap transport/storage providers and tune polling via JS filters.
– Important limits: Initially restricted to two simultaneous collaborators and disabled when metaboxes are present (a sign for plugin authors to move away from metabox-based UIs). It’s opt-in rather than enabled by default after some community pushback.
– Who should care: This is most useful for enterprise teams and newsrooms. Casual solo writers may find it unnecessary or intrusive, but it’s a big step toward collaborative publishing in core WordPress.
2) AI foundation: Connectors API + wp_ai client
– What it is: Instead of shipping a specific AI feature, core provides the scaffolding to connect to external models and services.
– Key parts: A new Connectors admin screen to manage API keys (OpenAI, Anthropic, Google, etc.), a Connectors API for plugins to reuse, and a provider-agnostic PHP helper (wp_ai_client_prompt()) to send prompts to LLMs.
– Why it matters: Developers can add AI features without building credential management from scratch. WordPress positions itself as a neutral orchestration layer for AI services rather than a single-vendor solution.
– Who should care: Developers and sites planning to integrate AI-powered workflows; it lowers friction for building AI features safely.
3) Visual revisions
– What changed: The revisions view is now embedded in the editor with a timeline slider, color-coded change highlights (added = green, modified = yellow, deleted = red), a minimap on the scrollbar, and a Restore button when viewing history.
– Trade-offs: It’s more approachable for non-technical users, but it doesn’t show source HTML and only compares a chosen revision to the immediately preceding one (no arbitrary two-way diffs like the old screen). Some long-time revisons users may miss the old capabilities.
– Who should care: Editors and content managers who want quicker, visual rollback and inspection without leaving the main editing screen.
Developer standouts
– PHP-only block registration: You can now register blocks entirely in PHP (register_block_type with autoRegister + render_callback). No build step required for simple server-rendered, non-interactive blocks.
– Pattern overrides for custom blocks: Synced patterns can now let specific content change per instance (previously limited to a few block types). Useful for client work and reusable layouts.
– Client-side Abilities API: The JS counterpart to server-side abilities (packages @wordpress/abilities and @wordpress/core-abilities) that helps manage capability state in the browser and hints at future agent/AI integrations.
– Custom CSS per block instance: A CSS input in the block sidebar that accepts declarations only (use & for nesting), making it easier to style individual block instances without theme edits.
Design and content-editing wins
– Navigation overlays: Better control of mobile menus with built-in overlay patterns, toggles for submenu visibility, and the ability to create pages directly from the Navigation block.
– Content-focused pattern editing: Patterns default to a content-only mode where clients can edit text/images without breaking layout; detach to get full control if needed. Great for safer client handoffs.
– Viewport-based block visibility: Show or hide any block per device (desktop/tablet/mobile) from the toolbar — functionality that previously required plugins.
Command Palette reminder
WordPress now includes a global Command Palette (⌘K / Ctrl+K) available anywhere in the admin to quickly find settings, tools, and navigation.
Verdict: good release
Overall, 7.0 is a strong release. Some features (real-time edit limits, visual-revisions trade-offs) might not suit every user yet, but the direction is deliberate: collaboration, extensible AI integration, and improved editing UX. The Connectors/AI architecture is the most forward-looking item — it lets the ecosystem innovate while core handles the plumbing and neutrality.
I’m excited to see what developers build on top of the AI connectors and how the collaboration tools evolve. If you’re a developer or run a multi-editor site, there’s a lot here to explore; if you’re a solo blogger, most changes are nice-to-have for now.
What do you think of WordPress 7.0? Which feature would you use first?
P.S. If you want to speed up your site while testing new features, consider joining a crash course on WordPress performance optimizations to reduce load times and improve UX.
