Every site looks designed on launch day. The test is what it looks like two years and three hundred edits later. The difference between a site that ages well and one that decays is not editor discipline — it is whether the design shipped as a system the editor works inside, or as a set of pages the editor works on.
1. Put the design decisions in theme.json
WordPress’s theme.json defines the palette, type scale and spacing the editor offers — and just as importantly, what it does not offer. Trim the colour picker to brand colours only, disable custom colours, define the font sizes. Every option you remove is a future inconsistency that cannot happen. Tokens beat guidelines because tokens are enforced.
2. Ship layouts as block patterns
A block pattern is a pre-built arrangement — a hero, a pricing band, a testimonial row — that an editor inserts whole. Build one pattern per layout your design actually uses, with real spacing and structure baked in. Editors go from “design a page from scratch” (where decay begins) to “assemble a page from approved parts” (where consistency lives).
3. Lock structure, free content
Block locking lets a pattern’s skeleton be fixed — blocks cannot be moved or removed — while text and images stay editable. This is the crucial balance: an editor can rewrite the headline but cannot delete the column it lives in or nudge its spacing. Freedom exactly where content needs it, guardrails everywhere else.
4. Use template parts for the site frame
Header, footer, and repeating page sections belong in template parts — edited once, updated everywhere. When the frame lives in one place, a rebrand or a nav change is one edit rather than an archaeology dig across forty pages.
5. The payoff compounds
A pattern-based system makes new pages faster to build, redesigns cheaper (restyle the tokens and patterns, and pages follow), and onboarding trivial — a new editor cannot really do the wrong thing. It is the least visible part of a build and the part clients thank us for a year later.