A Website Your Client Can Edit Alone

The test

You want to change one sentence on your homepage. You send an email. You wait two days. You get back "I'll handle it next week".

This is not a service problem or an attitude problem, and that is exactly why switching suppliers will not fix it. It is a technical decision that was made the day the site was built, and it keeps charging you every month.

Why this is architecture, not service

Text on a website has two possible places to live.

Inside the code. The sentence is written in a file, alongside the instructions that assemble the page. Changing it means opening the file, editing, checking nothing broke, and publishing again. That is developer work, even for a single word. So it joins a queue, and so it has a price.

In a database. The sentence lives in a row in a table. The site reads it as it loads. Changing it means opening an admin screen, typing, and saving. The change is live. No deploy, no developer, no queue.

This difference is invisible when you look at a finished website. Both sites look completely identical. The difference shows up only on the first day you ask for a change.

"I have a CMS" is not an answer

Plenty of sites are presented as "managed", while in practice only a small part is genuinely editable. A common case: a full admin system exists, but the homepage headline, the numbers in the benefits section and the button labels were written directly into the design, so they are locked.

The simple test is not "is there a CMS?" but: ask to change the main headline and the text on the primary button, and see what happens. If you can, you have a manageable site. If the answer is "that is in the code", you do not.

And no, not everything should be open

People often conclude that the fix is to make everything editable. That is a mistake, and I do not recommend it.

An admin screen where every colour, spacing value and font size can be changed is an admin screen where the site can be destroyed in one click, usually by accident. What should be open:

• Every piece of customer facing text. Headings, paragraphs, buttons, error messages, legal content.
• Images and media, with a fixed maximum size so the layout cannot break.
• Lists that grow over time. Projects, testimonials, articles, team members.
• Order. What comes first and what is hidden.

What is better left locked: the layout itself, the colour system, and the typography. Those are design decisions, not content, and they are what keeps the site coherent.

The bonus nobody mentions

When text lives in a database, it stops being scattered. A phone number that appears in five places comes from one source, so you cannot change four and forget the fifth. That is not just convenience, it is an entire class of mistake that stops happening.

The same goes for a second language. When content is managed, an English version is another field next to the Hebrew one. When content is in code, an English version is a project.

What to ask before you sign

1. What percentage of the text on this site will I be able to edit myself, without contacting you?
2. Does that include the homepage headline and the button labels?
3. How long after I save does the change appear on the live site?
4. If I delete text by accident and save, what happens? Is there a way back?
5. What happens when I need to add an entirely new page?

The answer to the fourth question reveals a lot. A serious system will not let an empty field wipe out live content.