A year into WordPress's block editor being the default, editorial teams on several client sites had settled into using it comfortably, but were still building complex layouts — a three-column feature callout, a pricing table — from individual blocks each time, which was slow and produced inconsistent results between editors.
We started shipping curated block patterns bundled with client themes: pre-arranged groups of blocks, styled to match the site's design, that an editor can insert as a single unit and then customize the content of. It has cut the time editors spend building common layouts significantly, and more importantly kept those layouts visually consistent across the site regardless of which editor built them, since the structure and styling come from the pattern rather than being assembled by hand each time.
How we built the patterns themselves
Each pattern started as a real layout an editor had actually requested — a three-column feature callout used repeatedly on one client's news section, for instance — built once in the block editor, then registered as a reusable pattern through WordPress's pattern registration API rather than left as a one-off. This grounded every pattern in an actual, demonstrated editorial need rather than us guessing upfront at what layouts editors might hypothetically want.
Training editors to use patterns instead of rebuilding from blocks
Beyond just making patterns available, we ran a short walkthrough session with each client's editorial team specifically demonstrating how to insert a pattern versus assembling the same layout from individual blocks, since a pattern that exists but that editors do not know to reach for provides no actual benefit over the old block-by-block approach. A couple of editors initially defaulted back to old habits out of familiarity before the patterns became a natural part of their workflow, which is why we now include this walkthrough as a standard part of every project that ships with custom patterns rather than assuming a pattern's existence in the editor's inserter panel is discovery enough on its own.
Measuring the actual time savings
On one client's news section specifically, we timed how long it took an editor to build the three-column feature callout from individual blocks versus inserting the equivalent pattern and adjusting only its content, and the pattern-based approach was several times faster for a layout of this complexity, which matched what we expected but was worth confirming with an actual side-by-side comparison rather than assuming the intuitive benefit held up under a real timed test.