Company Website Build & Deployment Platform

Challenge

A consultancy's website has to be as dependable as the work it advertises. Uploading files by hand, or a pipeline that tests one build and ships another, is how small sites quietly break — and a broken contact form is a lost enquiry nobody hears about.

Approach

One registered pipeline builds the site once, runs the full gate suite — linting, HTML validation, structured-data checks, accessibility and responsive-breakpoint checks, unit tests, a Lighthouse regression check and an end-to-end browser suite — and promotes that single tested artifact through dev, testing and production. No environment ever runs a different build from the one that passed. After every production deploy an automated smoke check confirms the live site, its availability data and its API are healthy, and changed pages are submitted to search engines automatically. Routine operations — credential rotation, availability sync, analytics housekeeping — run on schedule and report their own failures with enough context to act on. Bot and abuse protection is applied server-side to every form, and a strict content-security policy blocks script injection in the browser. Cloudflare fronts DNS and caching, with the cache purged automatically for changed files on each release.

Outcome

• 665 production deployments since March 2026 (to 15 October), each behind a one-click approval and the full test suite; a rollback is a pull-request revert
• The suite on 16 October 2026: 2,589 C# tests, 323 Node unit tests and 708 Playwright browser tests
• Every deploy is traceable to the run and commit that produced it
• Performance, accessibility and SEO checked on every release, not occasionally
• A gate that shows green is a gate that actually ran — unwired pipeline definitions were removed after they caused a near-miss

Where judgement mattered

• Build once, deploy the same artifact everywhere
• A health probe that checks real dependencies, not just whether the server answers
• Protection in the browser and on the server, rather than relying on developers remembering to sanitise every string
• Keyless, federated authentication for the pipeline's Google integration — nothing to rotate, nothing to leak