Looking after client websites
Not every website needs a rebuild. Some businesses have a site that works well, but nobody left to look after it. I take over the care of such websites, older and newer, on WordPress and on a headless CMS, no matter who built them.
- Client
- Several businesses, websites built by other developers
- Scope
- System and plugin updates, backups, bug fixes, new language versions, new features and sections, help for the client team
- WordPress
- Strapi
- Headless CMS
What businesses come with
The developer who built the site has disappeared or moved on. The site works, but nobody updates the system, nobody knows how to add a new page, and every small change means looking for a developer all over again.
These are most often WordPress or headless CMS websites, sometimes several years old, sometimes quite new.
What I do
I start by reviewing the site: what works, what is outdated and what could break. Then I take over the day-to-day care.
- Updates to the system, plugins and dependencies, with a backup before every change
- Help when something stops working or the team does not know how to change something
- New language versions and translated content
- New features and sections when the business needs them
- Speed and security fixes spotted along the way
No rebuild for its own sake
I do not push for a new website if the current one does its job. I develop what is there, and suggest a rebuild only when keeping the old site running costs more than a new one.
Screenshots
