WordPress 7.0 feels like a statement release — either the most ambitious redefinition of what WordPress wants to be, or simply a huge evolution in features. It’s the most notable directional shift in years: WordPress is moving beyond single-author blogging workflows toward collaboration, a neutral AI layer, and more visual editing tools.
Release snapshot
Current planned release date: May 20, 2026.
1. Real-time collaboration (RTC)
The headline feature in 7.0 is real-time collaboration: multiple people can now edit a post or page and see others’ changes as they happen — a Google Docs-style experience. Key technical points:
– Conflict resolution uses CRDTs (Conflict-free Replicated Data Types).
– The system relies on HTTP polling to maximize compatibility across hosts.
– Initially limited to two simultaneous collaborators to reduce load on shared hosting.
– Hosting providers can swap transport and storage, and developers can tweak polling via JS filters.
– The feature is disabled when metaboxes are present, signaling plugin authors to update how they integrate with the editor.
Should you care? This is most valuable for enterprise teams and newsroom setups. Casual bloggers and many solo creators may not find it useful — and some writers will prefer working alone on drafts. The feature was originally intended to be on by default but is now opt-in after feedback. This is a first iteration; expect the experience to mature.
2. AI foundation: Connectors API and WP AI client
Rather than shipping WordPress-branded AI features, 7.0 provides the scaffolding for AI integrations. The idea is neutrality: core offers a way to connect to external AI services without tying users to a single vendor.
What’s included:
– A new Connectors screen in wp-admin for managing API keys to services like OpenAI, Anthropic, Gemini, etc.
– A Connectors API plugins can use to standardize handling of external service credentials.
– A provider-agnostic helper (wp_ai_client_prompt()) that lets developers send a prompt to whatever configured LLM client is available.
Should you care? For developers this is a big win: it removes a lot of repeated work around credentials and request plumbing, letting devs build AI-enabled features more quickly. For end users, it opens the door to many third-party AI features while keeping WordPress vendor-neutral.
3. Visual revisions
Revisions are more visual and integrated into the editor instead of living on a separate admin page. Highlights:
– A timeline slider in the header to browse versions.
– Color-coded diffs: yellow for modified, red for deleted, green for added.
– A minimap on the scrollbar showing where changes occur.
– A Restore button appears when browsing history.
Should you care? The new UI may be friendlier for non-technical users, but it also drops some capabilities of the old revisions view: you don’t see raw HTML source, and you can’t arbitrarily compare any two versions — only a selected past version against its predecessor. Longtime revision users may miss the older, more technical comparison tools.
Developer standouts
– PHP-only block registration: You can now register blocks using only PHP (register_block_type with autoRegister and a render_callback), eliminating the need for a JS build step for simple server-rendered blocks.
– Pattern overrides for custom blocks: Pattern Overrides now work with any block that supports Block Bindings, not just core text and image blocks. That’s useful for client projects that reuse synced layouts but need instance-specific content.
– Client-side Abilities API: A JS counterpart to the server-side abilities introduced earlier, split into @wordpress/abilities (state) and @wordpress/core-abilities (REST connector). Mentions of browser agents and integrations hint at future AI agent workflows.
– Custom CSS per block instance: Blocks can now have CSS entered directly in the sidebar. You write declarations (no selectors) and use & for nesting — convenient for fine-grained styling.
Design and content editing wins
– Navigation overlays: More control over mobile hamburger menus with built-in patterns, an always-visible submenu option, and the ability to create pages from the Navigation block.
– Content-focused pattern editing: Patterns default to a content-only mode with editable fields in a simplified sidebar. Authors can detach patterns when they need full block access. This is useful for client handoffs to prevent accidental layout breaks.
– Viewport-based block visibility: You can show or hide blocks per device type (desktop, tablet, mobile) from the toolbar — functionality that previously required plugins.
Command Palette reminder
WordPress now includes a global Command Palette (invoke with ⌘K / Ctrl+K) for quickly finding settings and navigating the editor — handy for power users.
Verdict: a solid, forward-looking release
Overall, 7.0 is a good release. Not every feature will excite every user, but the direction is clear: collaboration, neutral AI infrastructure, and more approachable visual tools. The AI connectors in particular are promising because they let the community build a wide variety of AI-powered plugins without core locking users into a single model.
I’m excited to see how developers and hosts expand these foundations in the months ahead. What are you most interested in trying from WordPress 7.0?
If you want practical tips next, consider a short crash course on speeding up your WordPress site — small changes can cut load times dramatically.