I have never liked handing a client a blank page and calling it freedom.
A blank page looks flexible, but it often creates uncertainty. The client has to decide the layout, the hierarchy, the spacing, the order of content and the call to action before they can even publish the thing they came to write. That might be fine for someone who works with content every day. For many business users, it slows the work down and increases the chance that the page drifts away from the rest of the site.
This year I have been thinking more about patterns as a better starting point. Not because every page should look the same, but because most websites have recurring content needs. Service introductions, testimonials, feature comparisons, team sections, enquiry blocks and article listings all appear again and again. If those structures are already thought through, the editor can focus on the content instead of rebuilding the page from memory.
A Pattern Is A Decision Saved For Later
The useful thing about a pattern is that it stores a decision. It says this kind of content usually needs this shape. The editor can still change the words and images, but the underlying structure has already been tested against the design system and the way the site should behave.
That matters because a website is maintained over time by people who were not always part of the original design conversation. A pattern carries some of that conversation forward. It gives the next person a sensible place to start.
I prefer patterns that describe real publishing needs. A pattern called ‘Two Column Text And Image’ is usable, but a pattern called ‘Service Introduction’ is more helpful because it describes intent. The editor understands when to use it, not just what it looks like.
Too Many Patterns Creates Another Problem
There is a temptation to turn every design variation into a pattern. I try to avoid that. If the pattern library becomes too large, the editor is back to making design decisions they may not feel confident making. The choice is no longer a blank page, but it can still become a wall of similar-looking options.
A smaller set of clear patterns is usually better. I would rather give someone eight patterns they understand than thirty patterns they have to test every time. The goal is not to show how many layouts the system can produce. The goal is to make publishing easier without damaging consistency.
This is where real project use helps. The best patterns often appear after seeing what the client actually needs to publish. A pattern that looked important during design might rarely be used. Another that seemed minor might become part of weekly content work.
Patterns Should Reduce Training
A good pattern reduces how much someone needs to remember. The section already has the right spacing, heading level, button style and image treatment. The editor still needs to understand the content, but they do not need to reconstruct the design each time.
That changes the handover conversation. Instead of explaining how to build every section from individual blocks, I can explain which patterns exist and when they should be used. The handover becomes less technical and more editorial. That is usually a better conversation for the person who will actually maintain the site.
<!-- wp:pattern {"slug":"theme/service-introduction"} /-->The technical implementation may be simple, but the thinking behind the pattern is not. The pattern represents a decision about how the business presents a specific type of content.
What I Take From It
I think patterns are one of the more practical ideas in modern WordPress because they recognise how websites are used after launch. A business does not only need a designed homepage. It needs a way to keep publishing pages that feel like they belong to the same site.
A blank page gives freedom, but it can also pass too much responsibility to the editor. A good pattern gives direction. It helps someone start in the right place, then lets them focus on the message rather than the mechanics of layout.