How to let a client edit a static website.
A static site has no login and no editor. Here are the ways to give a client one, and how to choose.
In shortTo let a client edit a static website, you either make the changes for them, add a Git-based or headless CMS that writes to the site’s content, or use a host with a built-in editor such as heyweb, where the client changes content by chat.
The four options
Ordered from least to most independence for the client.
| Option | Setup | What the client does | Fits when |
|---|---|---|---|
| You make the changes | None | Writes you an email | Changes are rare and you bill for them |
| Git-based CMS | Configure fields for your files, set up builds | Fills in forms in an admin panel | A developer maintains the site |
| Headless CMS | Model content, connect an API, set up builds | Fills in forms in an admin panel | Content is structured or shared across channels |
| Host with a chat editor | Upload the site | Asks for the change in a chat | A small designed site and a client without technical interest |
heyweb is the fourth option. Its client chat is in early access. The second and third are compared in heyweb or a headless CMS.
Decide these three things first
What is content
List what the client will really change: hours, prices, team, menu, news. It is usually shorter than expected.
What must not change
Navigation, legal text and anything that carries the layout. Lock it, whichever option you choose.
How mistakes are undone
A client who can undo edits with confidence. Make sure the way back does not go through you.
Why forms are harder than they look
An admin panel with fields is exact, and it asks the client to learn where each sentence of their website lives. For a site that changes twice a month, most clients forget between visits and write an email anyway.
A chat turns that around. The client says what should be different, in their own words, and the editor finds the place. The price is that it suits content changes, not page building.