WordPress 7.0 is a major release with several visible editor improvements, developer-focused changes, and a new approach to AI integration. Whether you run a simple blog or a multi-author publication, these updates change how you build, edit, and manage content.
Overview
This release introduces a centralized AI Connectors screen, a refreshed admin experience with smoother transitions, responsive block visibility, per-block custom CSS, smarter visual revisions, and new native blocks (Icons, Breadcrumbs, Headings). Many developer APIs and tooling improvements are included as well.
AI Connectors: centralized AI integration
– New Settings » Connectors screen lets you install and authenticate AI provider packages (OpenAI, Google Gemini, Anthropic) once for the whole site. Plugins and themes using the WordPress AI API can reuse this connection without separate API keys.
– Credentials are stored securely and communication is standardized.
– To disable all AI features site-wide, add define(‘WP_AI_SUPPORT’, false); to wp-config.php.
Admin refresh and command palette everywhere
– The admin UI has updated colors, typography, and faster, app-like navigation that avoids full page reloads between many screens.
– The Command Palette (press ⌘K or Ctrl+K) is now available from any admin screen for fast navigation and actions. It’s optional—menus still work as before.
Responsive block visibility by device
– You can now show or hide any block on desktop, tablet, or mobile directly from the block toolbar or inspector—no CSS required.
– Blocks with visibility rules show an icon in List View. Visibility controls are also reachable from the Command Palette.
– You can apply different styles per breakpoint and customize breakpoints if needed.
Smarter visual revisions
– Revisions now include side-by-side visual diffs with color-coded outlines: green for added blocks, red for removed blocks, yellow for changed settings; text additions/removals are highlighted inline.
– The inspector sidebar lists changed block attributes so you can see exactly what was modified.
– This makes reviewing and rolling back changes far easier, especially on multi-author sites.
Custom CSS for individual blocks
– Each block now has a Custom CSS field in the Advanced panel. Styles entered here apply only to that block instance and render live in the editor.
– CSS is stored with the block, so it moves when you duplicate or move the block.
– Only roles with the edit_css capability (typically Admins and Editors) see this field. Block authors can opt out if needed.
New native blocks
– Icons block: insert and style SVG icons from the WordPress icon library (resize, recolor, spacing). Support for registering custom icon sets is planned for a future release.
– Breadcrumbs block: add automatic breadcrumb trails to templates without a plugin; developers can customize via filters.
– Headings block: manage H1–H6 levels from a single block with sidebar level switching, improving accessibility and structure.
Customizable navigation overlays
– Mobile menu overlays in the Navigation block are now stable. A guided “Create overlay” flow provides pre-built designs for mobile navigation.
– Theme developers can register a navigation-overlay template part for additional control in the site editor.
Pattern editing improvements
– Block patterns default to content-only editing mode, showing a simplified view focused on text and image swaps rather than full design controls.
– Advanced users can restore full pattern access via a filter if they prefer.
Gallery lightbox navigation
– The Gallery block’s lightbox now includes back/next buttons and arrow-key navigation so visitors can browse images without closing the lightbox.
Under the hood: developer and tooling changes
– theme.json pseudo-element support: themes can style :hover, :focus, :focus-visible, and :active states in theme.json for cleaner theming.
– PHP-only block registration: blocks with basic server-driven behavior can be registered using only PHP, reducing JS overhead for simple cases.
– Block Selectors API: blocks can declare selectors.css in block.json to control how Global Styles target elements.
– Font Library: new dashboard page to manage, upload, and install fonts across all theme types (block, hybrid, classic).
– WP-CLI 3.0: new command sets including wp block (read-only block access) and wp ability for the AI Abilities API.
– wp-env: phpMyAdmin support on the Playground runtime by enabling “phpmyadmin”: true in .wp-env.json.
– Site Health includes OPCache info under Tools » Site Health » Info » Server to help diagnose PHP opcode caching issues.
– Iframed editor: editor switches to an iframe when all blocks are Block API v3+, improving stability and performance while preserving compatibility with older blocks.
– More secure user registration defaults: Administrator and Editor roles removed from the default role dropdown to avoid accidental assignment. Site Health notifies if these were previously set.
– PHP requirement: minimum PHP 7.4; PHP 8.3 or 8.4 recommended for performance and security.
Miscellaneous enhancements
– Cover blocks now accept video URLs as backgrounds without uploading files.
– Text alignment has been standardized across eight additional post-related blocks for consistent behavior.
– Interactivity API gains a new watch() function to simplify interactive block side effects.
– DataViews and DataForm packages received updates including new layouts, validation, and grouping; developers should review breaking changes.
– Client-Side Media Processing preview was moved to a standalone plugin and is not included in core.
Final thoughts and upgrade advice
WordPress 7.0 delivers practical editor features and solid developer improvements. The Connectors screen lays groundwork for standardized AI integration, while responsive visibility and per-block CSS answer long-standing content-building requests.
Before updating:
– Backup your site and database.
– If you manage a critical site, test 7.0 on a staging environment first.
– Check plugins and themes for compatibility, especially custom blocks and those interacting with the editor APIs.
After upgrading, explore the Connectors screen, try block visibility and per-block CSS, and use visual revisions to review recent changes. These improvements aim to make content creation faster and more precise while giving developers cleaner APIs and tools.
If you want help planning an update or checking compatibility, I can provide a checklist tailored to your site.
