Designing a website your team can keep up to date
Give editors a clear way to make routine changes with content models, reusable sections, and a practical handover.
Maya Ellis · Co-founder & Design Director
· 4 min read

A website stays useful when the people closest to the work can update it. If publishing a new case study requires a developer every time, updates soon become a backlog.
Start with the changes your team makes in a normal month. Those tasks will tell you what needs to be editable and what should stay consistent across pages.
Design around the work editors actually do.
List changes such as swapping a project image, editing a service description, or posting a new role. Ask who makes each change and what they need to finish it.
Use a recent update as a test case. Walk through who supplied the copy, who approved it, and where the process stalled.
Design the editing experience too. It determines how the site grows after launch.
Give repeatable information a home.
A case study has a title, summary, cover image, and a set of details. Separate those fields so the same project can appear in a listing and on a detail page.
Name fields in the language editors already use. Add short guidance where image crops or text length affect how an entry displays.
Build reusable sections around a purpose.
Use a small set of blocks for common tasks such as introducing a page, listing projects, or answering questions. Each block should have an obvious reason to exist.
Preview the blocks with real content. Try long headings and missing optional images so the design accommodates what editors will publish.
Let the next editor try it.
Give someone outside the design team a routine publishing task and watch where they pause. A confusing field name is easier to fix now than after handover.
Check the preview on a narrow screen and confirm that drafts can be reviewed before they appear on the live site.

Make publishing responsibilities clear.
Decide who owns page copy, who checks new images, and who can publish. Put those decisions near the editing workflow so they are easy to find.
For the first few updates, ask editors what they had to look up. Use their answers to improve the instructions and defaults.
Teach the workflow by publishing together.
Use a real case study or announcement for the handover. Record the steps from draft to preview to publication while they’re fresh.
Leave a short reference covering image sizes, accessibility basics, and what to do when a page needs a new layout.
A handover checklist for editors
- List the routine updates.
- Name the people who review and publish.
- Test a real entry from draft to live.
- Document image and accessibility guidance.
- Agree how to request new components.
Try one real update before launch. It will show you whether your team has the tools and context to keep the site useful.


