When a client's website goes live, a handful of small jobs fall due the same afternoon. We have put them behind a single tap in our admin system, and it only works once the live site has passed its checks.
What they needed
In this case the client is us. Every site we build ends the same way. It goes live, and a launch checklist starts running in our heads: add it to the portfolio, take screenshots, write it up, perhaps post about it, and make sure nobody does any of that twice.
Done by hand, those steps get skipped when the next project is already waiting. We wanted the routine parts to happen reliably, without losing the one rule that matters: a site is announced only when it is genuinely up.
What we did
We added a launch trigger to the admin system we use to run client work. Before anything goes public, it checks the production domain:
- the domain name resolves
- the site has a valid SSL certificate
- the site answers with a healthy 200 response
If any check fails, nothing is announced. If all three pass, one tap starts the launch work:
- a new entry in our portfolio
- a request for fresh screenshots of the live site
- a planned case-study article, with a hero image
- an optional Facebook announcement
Every launch is recorded in our admin system, so the same site is never announced twice.
What it means day to day
Most of this is invisible to the client, and that is the point. A site that has just launched gets the same treatment every time: checked first, then photographed, listed and written up, without anyone having to remember the list.
A person still decides when a site is ready and presses the button; the system handles the steps that follow.
Our portfolio is here, and if you have a site in mind, get in touch.
Want something like this for your business? We're in Scarborough - websites start at £49.
Start a conversation