Vania Nettleford
Engineering Lab

The website thatstopped changing

3 min read← All posts

Launch day is the best day of a website’s life. Everything is current — the hours are right, the menu is the menu, the people on the team page actually work there. Someone proofread it, someone else clicked every link, and it went live feeling finished.

Then real life happens. Hours change for the summer. A price goes up. Someone leaves, someone joins. A seasonal menu comes and goes. And the site… doesn’t.

Not because nobody noticed. Usually someone noticed months ago. And most small businesses don’t need a developer to change a sentence — the site is WordPress or Squarespace, and the owner can log in and edit it themselves. That’s supposed to be the whole point.

So why doesn’t it happen? Because editing the site means opening the builder, finding the right page, hunting for the block that holds the hours, and hoping you don’t nudge the layout out of shape while you’re in there. It’s a two-minute edit wrapped in a fifteen-minute errand, and it’s never the most urgent thing on the list. So it waits for a quiet day. Quiet days don’t come. The sentence stays wrong. Then another one joins it. After a while, the site isn’t describing the business anymore. It’s describing the business as it was on launch day.

You can spot it from the outside, the same way a stranger would. The hours say one thing and the door says another. The team page introduces someone who left last year. The news section’s newest item is old enough to be history. None of it is dramatic. That’s what makes it easy to miss — a site doesn’t break all at once, it just quietly stops keeping up.

The reason is usually structural, not personal. On a lot of sites, the words are tangled into the design: to change the text you have to open the thing that draws the page and edit inside it. So every small change carries the risk of breaking something visible, and changes queue behind everything else. The owner isn’t lazy. The setup just made a two-minute edit feel like a chore.

There’s a simpler shape, and it’s worth describing in plain words because it changes who can keep a site current. Keep the content — the hours, the prices, the names, the announcements — in one place, in plain text, in an editor the owner already knows how to use. Let the site pull from that place when it draws a page. Then changing the hours is changing the hours: the owner edits the text, the site updates, and nobody has to open the builder or worry about the layout. Developers call this headless, which is a stranger word than the idea deserves. The idea is just keeping the words separate from the frame that shows them.

This site runs that way, by the way — the content lives in WordPress, the pages are drawn separately — which is how I know the difference isn’t theoretical. The test of a site isn’t launch day. It’s the third time something changes.

A site that can be updated gets updated. Its hours match the door. Its prices match the register. The people on it are the people in the room. And because each change is small, none of them ever becomes a project — there’s no “website refresh” looming in the future, because the site never fell behind in the first place.

So the question worth asking about a website isn’t how it looks on the day it launches. It’s who can change it on an ordinary Tuesday, and how much friction stands between them and the edit. If the answer is “the owner, in about two minutes, without opening the builder,” the site has a future. If the answer is “eventually, when there’s a quiet day,” the site is already going stale — politely, quietly, one unchanged sentence at a time.