Website Development and Maintenance

Content types are remodelled rather than copied, so the new site is properly structured instead of a flat import. Templates have accessibility requirements built in, so every page inherits them, and editors get a publishing workflow they can use without raising a ticket.

The site is built on a headless CMS, where content is authored once and delivered to every channel through an API. Static-first publishing keeps pages fast and the attack surface small, and patching is managed at the platform level from the very first release.

Content, URLs and compliance settings move across together, with redirects mapped so inbound links keep landing where they should. The old site stays live until the new one is accepted, so the cutover is a clean switch rather than a gap in service.

Patching, accessibility and platform upgrades continue after launch, while defacement monitoring watches the live site and alerts on any unauthorised change. Because hundreds of sites can share one platform, each upgrade is routine work done once rather than a separate project for every site.