A site changes after launch: content, dependencies, and the occasional defect. Maintenance is the agreement for who does that work and how requests are raised.
Website updates
Content structure changes, small template adjustments, and dependency updates on an agreed cadence.
Security improvements
Patching, review of exposed files, and practical hardening of the hosting environment.
Performance optimization
Finding the pages or queries that are slow and fixing the cause, not only the symptom.
Bug fixes
Defects reproduced, corrected, and noted so the same report is not lost.
Backups
Scheduled copies of files and the database, with a restore step that has been tried.
Technical support
A channel and response expectation written into the support agreement, rather than an informal promise.
Key features
A request log
Every change has a date and a short description.
Known backup location
You know where copies are kept and who can restore them.
Patch cadence
Framework and library updates are not left until something breaks.
Access hygiene
Former accounts are removed and production access is limited.
Benefits
- Less surprise. The site does not depend on one person remembering to update it.
- Faster recovery. A backup that has been tested is more useful than a backup that only exists.
- Room for small improvements. Minor changes do not each become a new project.
Technologies used
Our development approach
We start with access, backups, and a list of what is in production. Support work is then handled against that inventory, with changes recorded and deployed in a controlled way.