Designing a website someone else can run

The next editor is a user

The person updating a website is part of its audience. They need to understand where content lives, what can change safely and how to recover from mistakes. We consider their experience while designing the public site, rather than treating administration as a final task.

Make repetition explicit

If two elements serve the same purpose, they should usually share a component or content structure. This reduces drift and makes changes predictable. We give layers and fields names that describe their role. A future editor should not need to remember which anonymous frame contains the important setting.

Document the decisions that matter

Useful documentation answers practical questions: how to add a project, replace a video, change the accent colour and configure a form. Short steps and concrete examples work better than a catalogue of every possible setting. We place the guide inside the project so it stays close to the work.

Test the handover

Ask someone unfamiliar with the project to make a small update. Watch where they hesitate. Those moments reveal missing labels, unclear controls and unnecessary dependencies. A polished public site and a manageable editing experience are two parts of the same deliverable.