A custom block is a promise to an editor: this part of the page is safe to change. Most blocks I inherit break that promise. They expose every setting the developer could think of, and the editor gets a panel full of switches with no idea which ones matter.

Start from the page, not the block

Before I write any code I list every page the editors will make in the first year. A product page, an event, a team member. Each one becomes a pattern, and the blocks are only the parts those patterns need.

That list is usually shorter than anyone expects. Six patterns cover most marketing sites.

Fewer settings, better defaults

Every setting is a decision the editor has to make. If the design has one correct answer, the block should simply use it. I keep settings for things that really change from page to page: an image, a heading level, a link.

register_block_type( __DIR__ . '/build/product-story', [
  'supports' => [ 'color' => false, 'spacing' => false ],
] );

Name things the way editors do

Editors do not think in components. They think in "the bit with the quote" and "the coffee details". The block name, its description and its placeholder text should all use their words.

If an editor has to ask what a block does, the block has failed, not the editor.

Then I sit with one editor for half an hour and watch them build a page. That half hour finds more problems than any code review.