Three Layers of the Block Model
The relationship between WordPress blocks, patterns, and templates is easiest to read as a stack, starting from the smallest unit of content and building upward. A guide published by The WP Minute walks through this hierarchy, and its ordering makes the dependencies clear: patterns exist because of blocks, and templates exist because of patterns.
Blocks: the lowest common denominator
A block is the smallest unit of content in the editor. Everything else in the model is assembled from blocks rather than defined separately from them.
Patterns and synced patterns
Patterns are collections of blocks packaged for reuse across a site; they are the layer where content layout happens. Synced patterns take the same idea and add shared editing: one of these patterns can be edited together with the others it is linked to, which the guide describes as creating a "master pattern" for site-wide updates.
Synced pattern overrides sit on top of that. The feature locks a synced pattern while still permitting specific edits, so the shared structure survives without making every instance identical.
Templates as the page frame
Templates are full page layouts assembled from various patterns plus a small number of theme blocks — the equivalent of global components in a design system, such as a main navigation or a post loop.
Overrides and the 6.6 Release
Synced pattern overrides are newer than the rest of the model, having landed in the WordPress 6.6 release rather than being part of the original feature set.
Why Classic Theming Still Holds
For developers still running a classic/block hybrid setup, the block editor itself is not the sticking point — theming is. The preference is to keep classic PHP templates and the Template Hierarchy that comes with them, preserving a separation between theming and editing that the Site Editor and full-site editing do not obviously replace.
The hesitation is architectural rather than fearful: the connection between the Site Editor and the Block Editor exists, but it is not self-evident from the outside. Meanwhile, WordPress has kept classic, block, and hybrid architectures supported side by side, which is the flexibility that has long been its selling point — and a reason there is no pressure to adopt full-site editing wholesale, out-of-the-box.



