WordPress 7.0 is released, bringing a mix of user-facing improvements and developer-focused changes. We tested the beta and here’s a concise rundown of the most important additions and behavior changes you should know about.
AI Connectors: central AI integration
WordPress 7.0 adds a unified Connectors screen (Settings → Connectors) so you can install and authenticate AI provider packages from the dashboard. At launch the available connectors include OpenAI (ChatGPT), Google (Gemini), and Anthropic (Claude). Once connected, any plugin or theme that uses the WordPress AI API can reuse the same credentials, avoiding per-plugin key configuration. Connectors store credentials securely and standardize communication with AI providers.
Pro tip: to disable all LLM-related features site-wide, add define(‘WP_AI_SUPPORT’, false); to wp-config.php.
Admin refresh and navigation improvements
The admin interface gets visual polish: updated color schemes, clearer typography, and smoother transitions so many admin actions no longer trigger full page reloads. The Command Palette, previously limited to the editor, is now available everywhere — press ⌘K (Mac) or Ctrl+K (Windows/Linux) to quickly jump to pages, search posts, or run common actions without the mouse.
Responsive block visibility
A long-requested feature, block visibility per device is now built into the block editor. You can hide or show any block on desktop, tablet, or mobile from the block toolbar or inspector. Blocks with active visibility rules show icons in List View, visibility controls are accessible via the Command Palette, and you can set different styles per breakpoint. No custom CSS is required for common responsive adjustments.
Visual revisions and comparison tools
Revisions now include visual diffs: compare two revisions side-by-side with color-coded overlays (green for added blocks/text, red for removed, yellow for modified settings). The sidebar shows changed block attributes alongside the visual diff, making it much easier to review and revert edits — especially useful on multi-author sites.
Custom CSS per block
A Custom CSS field is added to the Advanced section of the block inspector. Styles entered here apply only to that block instance and are saved within the block, so they travel with it if duplicated or moved. Only roles with the edit_css capability (typically Administrators and Editors) see this field. Block authors can opt out via block.json.
New native blocks
WordPress 7.0 ships three new built-in blocks:
– Icons block: insert and style SVG icons from the WordPress icon library without a plugin; resize, recolor, and adjust spacing.
– Breadcrumbs block: auto-generate breadcrumb trails for posts, pages, and custom post types; includes filters for developers to customize items and taxonomy preferences.
– Headings block: unified handling of H1–H6 with built-in level variations and quick switching in the sidebar.
(Official support for registering third-party icon libraries is planned for a future release.)
Navigation overlays and pattern editing
Mobile navigation overlays are no longer experimental. The Navigation block includes a guided “Create overlay” flow and pre-built patterns. Pattern editing defaults to a content-only mode (isolate mode) that simplifies the interface for swapping text and images; developers can disable this behavior via a filter if they prefer full access.
Gallery lightbox navigation
The Gallery block’s lightbox now has back/next buttons and arrow-key navigation, making it easier for visitors to browse images without closing the viewer.
Developer and platform changes (under the hood)
– theme.json pseudo-element support: style :hover, :focus, :focus-visible, and :active states directly in theme.json for blocks and variations.
– PHP-only block registration: register functional blocks using PHP only (no JS required for basic server-side blocks).
– Block Selectors API: blocks may declare selectors.css in block.json to control how Global Styles scope CSS selectors.
– Dedicated Font Library page: a dashboard page to manage, upload, and install fonts across block, hybrid, and classic themes.
– WP-CLI 3.0: ships new commands including wp block (read-only) and wp ability for AI Abilities API management.
– wp-env: phpMyAdmin support on Playground runtime when enabled in .wp-env.json.
– OPCache info added to Site Health (Tools → Site Health → Info → Server) to help debug PHP opcode cache issues.
– Iframed editor: the editor automatically uses an iframe when all blocks in a post use Block API v3+, improving stability and performance.
– More secure user-registration defaults: Administrator and Editor are removed from the default role dropdown to reduce accidental privilege grants; Site Health will warn if your site used those defaults prior to updating.
– PHP requirement: minimum PHP 7.4; WordPress recommends PHP 8.3 or 8.4 for best security and performance.
Miscellaneous improvements and notes
– Cover blocks now accept video embeds via URL for background media.
– Text alignment standardized across additional post and term-related blocks.
– Interactivity API adds a watch() helper for cleaner side-effect patterns in interactive blocks.
– DataViews and DataForm packages include layout, validation, and grouping updates; plugin authors should review breaking changes.
– Client-Side Media Processing previewed during beta was removed from core and moved to a standalone plugin for continued development.
Real-time collaboration (RTC)
RTC was planned for 7.0 but was pulled before release due to concerns around race conditions, server load, and memory efficiency. It remains in development and is available to test via the Gutenberg plugin; it will ship when the approach is stabilized.
Final recommendations
Before updating, back up your site and, for mission-critical installs, test 7.0 on a staging site. Explore the Connectors screen, visual revisions, per-block CSS, and responsive visibility options — these are the changes most likely to affect content workflows. Developers should review theme and block APIs listed above and verify block.json declarations if they see editor changes after updating.
If you want help assessing compatibility or planning an upgrade workflow, tell me about your site (plugins, theme type, hosting) and I can suggest next steps.