Technical
WordPress Block Patterns: The Feature I Wish I Used Sooner
I ignored block patterns for the first two years of block-editor WordPress. I thought they were just templates with extra steps. I was wrong. Block patterns are the feature that makes WordPress genuinely usable for non-technical clients. Let me explain.
What They Actually Are
A block pattern is a pre-arranged group of blocks that a user can insert into any post or page with one click. They see a visual preview in the inserter. They click it. The blocks appear, configured and styled. They edit the content in place.
This sounds trivial. It is transformative. Without patterns, clients stare at a blank post and freeze. With good patterns, they pick the layout they need and start writing.
Where I Use Them
Every site I ship now has a pattern library curated for the client's needs. A services page pattern. A case study pattern. A team page pattern. A call-to-action pattern. Each one encodes the design system.
The client does not need to know about columns, groups, covers, or spacers. They pick a pattern. They write. Everything stays on brand because the pattern did the design work upfront.
// Register a pattern from a PHP file
register_block_pattern(
'mytheme/services-grid',
array(
'title' => 'Services Grid',
'description' => 'Three-column services layout',
'content' => file_get_contents(
get_template_directory() . '/patterns/services-grid.html'
),
'categories' => array('mytheme'),
)
);The pattern content lives in an HTML file I can edit in any text editor. Source-controlled, reviewable, diffable. That makes the pattern library a first-class part of the theme.
The Handoff Win
When I hand off a site, I show the client one thing: the pattern inserter. I walk through three patterns. They get it in five minutes. The usual hour-long training becomes a ten-minute overview.
Their edits stay consistent with the design because the patterns encode the rules. They cannot accidentally use the wrong heading hierarchy or the wrong spacing because the pattern already set those correctly.
Why This Matters
WordPress handoff quality determines whether clients stick with the site or bounce back to me every month. Patterns made handoff smoother than any other feature I have adopted. See the block patterns documentation for the full API.
The best features are the ones clients love without knowing the mechanics. Patterns are exactly that.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read