Beta 5 is out and RC1 ships tomorrow, so the WordPress 7.0 feature set is settled. Notes on pattern overrides reaching custom blocks, viewport controls landing in core, and why per-block custom CSS worries me.
The Connectors API gives WordPress one registry for external services, starting with AI providers. Notes on the init lifecycle, the unregister and register dance for overrides, and the keys that sit unencrypted in wp_options.
WordPress 7.0 can hide a block per viewport, but the block still renders and its assets still download. Notes on the new metadata shape and the server-side check I use to handle both formats.
WordPress 7.0 lets you write CSS on a single block instance from the inspector. Here is how the hash-based scoped class is generated, where the rule is stored in the block markup, and how to opt a block out in block.json.
Core bundles its own AI client in WordPress 7.0, so older AI Experiments builds fatal the moment you activate them. What is graduating out of experiment status, the LLM kill switch in Trac 64706, and how to load your own AI code without crashing.
In WordPress 7.0 unsynced patterns open in contentOnly mode by default, so any block without a content role goes uneditable. What to fix in block.json, what the new listView support gives container blocks, and how to switch the whole thing off.
WordPress 7.0 Beta 5 adds a Command Palette shortcut to the admin bar and closes more than 101 bugs. What the shortcut does, how to register your own commands with the API, and why I update beta sites with WP-CLI.
WordPress Studio added Xdebug support and a dedicated debug log toggle. Here is how I turn both on, the one-site-at-a-time catch, and the port your IDE has to listen on.
WordPress 7.0 moves width and height into block supports and adds dimensionSizes presets to theme.json. What goes in block.json, and which custom inspector controls you can finally delete.
WordPress 7.0 syncs the block editor through Yjs, and one classic meta box switches the whole thing off. Migrating meta to the REST API, swapping HTTP polling for WebSockets, and the block side effects that fire for every editor in the session.