WordPress 7.0 looks set to be one of the most consequential releases in years — a pivot from a single-author publishing tool toward collaboration, AI integration, and more visual content management.
Status check
Current release date: May 20, 2026.
1) Real-time collaboration (RTC)
The headline feature is live, real-time editing for posts and pages so collaborators see each other’s changes as they happen, similar to Google Docs.
Key points:
– Uses CRDT (Conflict-free Replicated Data Types) to resolve conflicts.
– Runs on HTTP polling for broad host compatibility; hosts can swap transport or storage.
– Initially limited to two simultaneous editors to reduce server load.
– JavaScript filters let developers tweak polling behavior.
– RTC is disabled when classic metaboxes are present, encouraging plugin authors to modernize.
Should you care? This targets newsrooms and enterprise teams more than individual bloggers. The feature is opt-in after feedback, and many writers prefer static drafts, but RTC is a major step that will evolve over time.
2) AI foundation (Connectors API + wp_ai_client)
Instead of shipping branded AI features, WordPress 7.0 provides the scaffolding so plugins and themes can integrate AI services consistently and safely.
What’s included:
– A Connectors screen in wp-admin to manage API keys for OpenAI, Claude, Gemini, and other providers.
– A Connectors API plugins can use for centralized credential handling (not limited to AI).
– wp_ai_client_prompt(): a provider-agnostic PHP helper to send prompts to LLMs.
Should you care? Yes, especially if you’re a developer. WordPress is positioning itself as a neutral orchestration layer: it won’t bake in a single AI provider but will make building integrations easier and more secure.
3) Visual revisions
Revisions are now integrated into the block editor with a visual, color-coded interface.
Highlights:
– Timeline slider in the editor header for browsing versions.
– Color coding: yellow = modified, red = deleted, green = added.
– A minimap on the scrollbar shows where changes occur.
– “Restore” replaces “Publish” when viewing history.
Should you care? This makes revision history more approachable for non-developers, but power users lose some capabilities: raw HTML view is gone and you can’t compare arbitrary revision pairs (only a revision against its previous state). Worth testing depending on your workflow.
Developer standouts
– PHP-only block registration: register_block_type supports autoRegister and render_callback so simple, server-rendered blocks no longer need a JS build step.
– Pattern overrides for custom blocks: synced patterns can keep layout while allowing instance-specific content across more block types with Block Bindings.
– Client-side Abilities API: a JS companion to the 6.9 server Abilities API (@wordpress/abilities and @wordpress/core-abilities) — a hint at future agent/AI workflows.
– Per-instance block CSS: add CSS declarations directly in the block sidebar; nesting via & works without writing selectors.
Design and content editing wins
– Navigation overlays: full control of mobile hamburger menus with overlay template parts, built-in patterns, submenu visibility toggles, and creating pages from the Navigation block.
– Content-focused pattern editing: patterns default to content-only editing with editable fields in a clean sidebar, and you can detach patterns to edit the full block tree — helpful for client handoffs.
– Viewport-based block visibility: toggle block visibility per device (desktop/tablet/mobile) from the toolbar without a plugin.
Command Palette
The Command Palette remains available everywhere with ⌘K / Ctrl+K for quick access to settings and actions.
Verdict
Overall, 7.0 is a strong, directional release. Not every feature will matter to every user, but the release clearly signals WordPress’s future: a neutral orchestration layer for AI and collaborative workflows, with improved visual tools for content teams. The Connectors API and provider-agnostic AI client are especially promising for developers, while RTC will be most compelling to collaborative and editorial environments.
Kudos to the core contributors. Which feature do you find most exciting or concerning in WordPress 7.0?
