MB, Musa Burke, home

All work

DSB Commercial Cleaning

A fast, secure website for a London-area cleaning company, live on its own domain.

DSB Commercial Cleaning home page, black and gold, with a close-up of a freshly cleaned carpet.
Year
2026
Role
Design, build and launch. Sole developer.
Stack
Astro, TypeScript, Tailwind CSS, React, Cloudflare
Live
dsbcommercialcleaning.co.uk

The brief

A carpet, upholstery and kitchen extract cleaning company needed a site that gets people to call, WhatsApp or ask for a quote. It covers London, Buckinghamshire, Berkshire, Hertfordshire and Oxfordshire.

What I built

  • One services page built from Markdown files, so a new service is a new file.
  • A coverage map drawn from ONS county boundaries. Picking an area shows a card with Call and a WhatsApp message that names the area.
  • A gallery with before-and-after pairs, and a reviews page with every review copied word for word.
  • A quote form with a honeypot, a time trap, length limits and a retry cooldown.

Security

The site ships an enforced Content Security Policy. Astro writes a hashed CSP <meta> into every page, and Cloudflare serves security headers from public/_headers. Only Astro’s own inline scripts can run.

Launch

Live on Cloudflare since 26 October 2026, with a business email, DMARC, Search Console and a Google Business Profile link.

What I learned

This is where I put everything together. I had a full plan and stuck to it. I asked the client all my questions at once, set up scheduled talks and built prototypes for them to react to.

I also learnt how to use AI properly. I treat it as a co-agent: it helps me build, teaches me as I go and helps me debug when I’m stuck, and I review everything it recommends before it goes in.

It was my first time using Web3Forms, getting my own domain through Namecheap, deploying it and connecting it through Cloudflare, and my first time doing proper security checks, including rate limiting. I also set up a business email address with SPF and DMARC, used a Cloudflare Worker for email routing around launch, and followed UK rules on handling user data.