I try to think about WordPress blocks from the position of someone editing the site when they are busy, slightly distracted and trying to get a page updated before the end of the week.
That is probably a better test than imagining the perfect editor during a training session. In a training session, everyone has time, the examples are clean and the person who built the site is usually nearby to answer questions. Real editing happens months later, when the original decisions are no longer fresh and the person using the CMS just needs the website to behave.
That is why I care less about giving editors endless freedom and more about giving them patterns that are difficult to misuse. A good block should make the right outcome the obvious one. It should not require the editor to remember spacing rules, image ratios or layout decisions every time they add content.
Freedom Can Become Work
A blank page builder can feel generous because it lets people create anything. The problem is that creating anything also means deciding everything. Which spacing should be used? How many columns should this section have? Should the image crop or contain? Is this button style correct for this page?
Those questions may feel small, but they become tiring when repeated across a website. They also create inconsistency because different editors will make slightly different decisions. The page may technically be editable, but the business loses the visual discipline that the original design was meant to provide.
I would rather give editors a smaller set of blocks that match real content needs. A case study intro. A service feature section. A testimonial pattern. A call-to-action block with limited variations. Those choices still give control, but they keep the important design decisions inside the system.
The Best Blocks Explain Themselves
A block should make its purpose clear without needing a separate conversation. If someone sees a field for eyebrow text, heading, description and button label, they should understand what the section is for. If a block includes six image settings and three layout switches, the editor may be technically empowered but practically uncertain.
This is where labels and defaults matter. A good default saves the editor from starting with an empty decision. A clear label prevents them from guessing what a field controls. Help text can be useful, but if every field needs explanation then the block is probably asking too much.
I also like blocks that limit dangerous choices. If a design needs a consistent image ratio, the editor should upload an image and let the block handle the display. They should not need to crop manually every time or remember the exact dimensions from a handover document.
Editing Needs To Survive New People
The real test of a block system is what happens when someone new inherits it. The person who attended the original handover may leave the business, change role or simply forget the details. The website still needs to be manageable.
That is why I think block design is part of long-term website ownership. The CMS should carry some of the project knowledge inside it. Patterns, defaults and restrictions can all help preserve decisions that would otherwise live only in memory.
This does not remove the need for documentation, but it reduces the amount of documentation people need to read before they can safely publish. The editing experience itself becomes a guide.
Retrospective Thoughts
When I design WordPress blocks now, I try to imagine the least ideal editing moment. The editor is short on time, the page needs to go live and nobody wants to break the layout. If the block still makes sense in that moment, it is probably doing its job.
That is the value of thoughtful constraints. They do not make the website less flexible. They protect the decisions that matter, so editors can focus on the content instead of rebuilding the design one section at a time.