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.
Telex is Automattic’s experimental tool for generating block themes from a prompt. What the output actually contains, the templates you have to ask for, and why I test every generated ZIP in Playground first.
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.
Chromium made the native select element styleable. This walks through appearance: base-select, the ::picker pseudo-element, sibling-index() for per-option maths, and the anchor positioning that makes a radial picker possible, without giving up keyboard support.
Four reasons I build layouts with Tailwind utilities instead of named CSS classes: the structure stays readable, one-off grids never need a name, and a context change is a class edit rather than a modifier.
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 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 is looking for volunteers on the Twenty Twenty-Seven default theme, which ships with 7.2 in December 2026. What the work actually involves, why the schedule is tight, and how a core theme differs from any client build.
Chromium ships corner-shape, so beveled and scooped corners no longer need clip-path or SVG masks. What each value does, how it pairs with border-radius, and how to ship it behind @supports while Firefox and Safari get plain rounded corners.