How we build websites
Design and build both happen in-house. You deal with the people doing the work rather than an account
manager relaying messages, and you see it taking shape rather than being presented with a finished thing
you have to react to.
Sites are built on our own content management system. That is unusual, and it is deliberate: there are no
third-party plugins in the stack that can stop being maintained, no theme that breaks on an update
somebody else shipped, and when something needs changing we change it rather than waiting for an upstream
release. If the CMS needs to do something it does not do yet, that is a development job we can take on
rather than a limitation you have to design around.
It also means the system is one you can actually use. Routine changes, such as text, images, a new page
or a staff update, are yours to make without coming back to us and without being able to break the
layout while you do it.
Launch is the start, not the end
A website is not finished when it goes live. That is the point at which it starts needing
attention. Certificates expire, software needs patching, and an unmaintained site becomes a liability
faster than most people expect. We keep it updated, monitor that it is up, and renew what needs renewing. That side of things is covered under security, and the
domain the site answers on is renewed on the same basis.
It is also built to grow. A structure that can take another section or another service without being
rebuilt is worth far more over five years than a design that only works at the size it launched at. If
what you need goes past pages and content, such as logins, records or a process with data behind it, that is web application development rather than a website,
and we do that too.