WordPress iteration issues get a real update schedule
The Gutenberg repo is changing how iteration issues work: a fresh issue per release, monthly updates before beta, weekly through RC, and a template that asks for scope and blockers up front.
The Gutenberg repo is changing how iteration issues work: a fresh issue per release, monthly updates before beta, weekly through RC, and a template that asks for scope and blockers up front.
WordPress 7.0 ships real-time collaboration over HTTP polling, which is fine until traffic picks up. Here is how I swap in a WebSocket transport with Yjs and the sync.providers filter, and what the auth side has to look like.
A decade of explaining why WordPress sites don’t feel like apps, and what 2026 changes: blocks described to an AI instead of scaffolded by hand, the Interactivity API handling state without page reloads, and theme.json holding the design system.
Gutenberg 22.8 adds collaborator selection highlighting and presence fixes to real-time collaboration, opens the Connectors registry API, and lets you style button hover and focus states in Global Styles. AVIF uploads and an admin bar Command Palette trigger come along too.
Gutenberg 22.7 puts editorial rules in the database instead of a forgotten PDF. A look at the wp_content_guideline post type, the REST endpoints, and what a persistent rule set gives an AI assistant.
WordPress 7.0 lets any block that supports Block Bindings take part in Pattern Overrides, not just the old Core list. You opt a custom block in with the block_bindings_supported_attributes filter.
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.
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.
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.