Central web teams face a standing dilemma: either every change goes through them — and the queue becomes the story — or academics edit their own pages and the visual identity dissolves one beige table at a time. Both failure modes come from the same place: an editor that allows everything.
Constraint as a kindness
Modern WordPress can lock the design system into the editing experience. Curated block patterns give editors ready-made sections that already follow the brand; theme settings remove the colour picker rather than asking people not to use it; templates hold the page structure while content stays editable.
- Editors choose from patterns, not blank canvases — faster for them, consistent for you.
- Roles scope who can edit structure versus content.
- Revisions mean nothing is ever truly broken.
- The brand survives without a single approval bottleneck.
Departments get autonomy, the institution keeps coherence, and the web team stops being a helpdesk for hyphenation. The technology for this is not exotic — it is native WordPress, configured with intent.
Setting it up: the practical recipe
Three WordPress mechanisms do nearly all of the work. Patterns: build each approved section once — staff profile row, news card grid, accented callout — and expose only those in the inserter. Theme configuration: lock the palette and type scale in theme.json so the editor simply doesn’t offer rogue colours or sizes. Roles: editors edit content; structure and templates stay with the web team. Add template locking for the pages where layout really matters, and the guardrails are complete.
Then train with a single page: every academic gets twenty minutes, edits their own profile live, and leaves with the one URL they need. Adoption follows usefulness, not memos.
Signs it’s working
- The web team’s queue shifts from ‘change this comma’ tickets to actual projects.
- Pages stop drifting off-brand, because off-brand isn’t selectable.
- Departments publish more, and more recently — staleness is mostly friction.
- New starters edit on day one without an induction session.
The deeper shift is cultural: the website stops being something done to departments and becomes something they do — inside boundaries the institution can stand behind.
