BZRP
The web presence for BZRP — a site whose quiet weeks and its loudest hour are separated by several orders of magnitude of traffic.
TODO: start with your role, and be precise about it. This is a recognisable name, which makes it the one project here where a reader will assume more than you said — 'I built the site' and 'I was one of four people at an agency who built the site' are both fine to have written, and only one of them is true. Say which, and say who else was on it.
The brief
TODO: what it had to do, and for whom. An artist site is rarely just a site — it is a release vehicle, and what it is for on a normal Tuesday is not what it is for on drop day.
Built for the spike
TODO: this is the engineering story, if it happened. A release turns a quiet site into a very loud one in minutes. What did you do about that — caching, static generation, a CDN, load testing — and what did you find out when it actually landed? If the traffic never came, say that too; a plan that was never tested is a different claim.
What I'd do differently
TODO: be specific and be honest — it is the difference between a case study and a brochure.