"But it was working fine!"

Your docs site is a production system and nobody's maintaining it

“But it was working fine!”

It was. Four years ago.

Recently a client called about their docs site. Sphinx 4 versions behind, dependencies with security vulnerabilities, relying on deprecated extensions, theme broken on new browsers, search noticeably slower.

The launch got budget. Content creation got budget. Someone even set up CI to build and deploy automatically. The team celebrated. Then moved on.

Framework upgrades, dependency updates, security patches? Nobody even brought them up. There was no line item for “keep the docs site alive.” Because it was alive. It was working fine.

Your docs site didn’t break

You just stopped keeping up with everything around it.

Every dependency you don’t update becomes a risk. Every framework version you skip makes the next upgrade harder. None of it is urgent on any given day. All of it is urgent four years later.

The decay is invisible. The site loads. The search works. The pages render. Until one day they don’t. Or they do, just slower, just slightly broken, just enough for users to notice before you do.

The cost equation

Keeping a docs site maintained is routine work. Not always simple, but manageable if you stay current. It just never wins against everything else on your roadmap. A few hours a quarter to update dependencies. A CI check for broken links. An annual framework upgrade before you fall too far behind. Call it 20 to 30 hours a year. Maybe $3 to 5K if you’re paying someone.

That client's docs were broken for at least three months before anyone flagged it. The fix took another six weeks. Four and a half months of slow search and a theme that looked off on half the browsers visiting it. All that time, the docs were quietly telling users you don't maintain your tools.

Your docs site is a production system

We all understand this for apps. Nobody ships a production app and walks away for four years. There are monitoring tools, dependency bots, upgrade cycles.

Docs sites get none of that. They get launched and forgotten. Then someone calls you four years later wondering why everything is broken.

It has users, dependencies, and security surface area. It deserves the same care.

That client’s site is fixed now. They’re on a maintenance plan. The kind of work that never makes headlines but means nobody has to make that call again.