If you’ve been building block themes lately, you know the drill: you check a reference table, see a checkmark, and assume a block supports what you need. Then you hit a wall. With the release of the WordPress 7.0 design tools roster, the core team has finally acknowledged that a simple “yes/no” doesn’t cut it anymore. We are moving away from hardcoded feature sets toward a dynamic, filter-based architecture that honestly makes my life—and yours—a lot easier if you know where to hook in.
I remember a project last year where I had to hack pattern overrides into a custom block. It was a mess of race conditions and transient data that never quite behaved. Now, as summarized in the WordPress 7.0 developer updates, the same mechanism that powers Block Bindings has been extended to Pattern Overrides. It’s cleaner, but it means our old lookup tables are evolving.
The Major Shifts in WordPress 7.0
The biggest change isn’t just a new block; it’s a renaming and an expansion. The Verse block is now the Poetry block. Beyond the semantics, WordPress 7.0 has introduced several heavy hitters to the core library: Accordion (with its sub-blocks), Breadcrumbs, and even a dedicated Math block. These aren’t just wrappers; they come with full-scale design support right out of the box.
Specifically, the block_bindings_supported_attributes filter is now the source of truth. Previously, we tracked Pattern Overrides (PO) and Block Bindings (BB) in a hardcoded column for Button, Image, Paragraph, and Heading. In 7.0, that’s gone. Support is now opt-in per block and per attribute, which is a massive win for custom block developers.
WordPress 7.0 Design Tools: Core Block Roster
Below is the updated cumulative list of design supports across the core block library. This summarizes changes between 6.1 and 7.0, specifically highlighting what has been added in the most recent cycles. This table is your first stop for debugging why a certain sidebar panel isn’t appearing for your users.
Technical Refactoring: Moving to Dynamic Attributes
If you are trying to find the WordPress 7.0 design tools logic in the source code, look at how attributes are registered. For those of us writing custom blocks, you can no longer just assume core handles the binding. You need to explicitly tell WordPress which attributes are “bindable.”
Here is a snippet to register support for a custom attribute using the 7.0 compliant logic:
<?php
/**
* Opting into Block Bindings and Pattern Overrides for custom blocks.
*/
function bbioon_register_block_binding_supports( $supported_attributes, $block_type ) {
if ( 'my-agency/custom-block' === $block_type->name ) {
$supported_attributes[] = 'customContent';
$supported_attributes[] = 'buttonText';
}
return $supported_attributes;
}
add_filter( 'block_bindings_supported_attributes', 'bbioon_register_block_binding_supports', 10, 2 );
?>Furthermore, check out the official dev notes on Pattern Overrides to see how this mechanism scales. It’s a complete departure from the legacy model where we had to manually enable these features.
Look, if this WordPress 7.0 design tools stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days, and I’ve seen these API shifts break more sites than I can count. Don’t let a “simple” core update turn into a weekend of debugging CSS regressions.
Final Takeaway for Developers
The roster is more than a list—it’s a roadmap. With the inclusion of tools like the Post Time to Read and Term Template blocks, WordPress is becoming a full-featured design system. Stop fighting the editor and start leveraging these core supports. If a block doesn’t support the property you need, use the RTC pivots and hooks discussed in previous notes to extend it properly.
” queries:[1677,1612,1603]},excerpt:{raw:
