CodeNXT Lab · Case study 04 / Starcolours Coating
Starcolours Coating.
Marketing site with a self-serve dashboard. Every image, price, and block of copy is editable by the owner.
01
The brief.
What they came with, in their words.
An industrial coating business whose previous site could only be changed by the person who built it. They had stopped updating it. The brief was less about design than about never having to make that phone call again.
02
Constraints.
The real ones, not the stated ones.
- The owner edits the site, not a marketing team and not a developer. Anything that needs an explanation will not get used.
- Prices and finishes change more often than the layout does, so content and structure had to come apart.
- Handover had to be real: they wanted to be able to replace us without replacing the site.
03
What we built.
The system, and what it runs on.
A self-serve dashboard sits over a content store, and the public site reads from it. Every image, price, and block of copy on the site is an entry the owner can change, with no build step and no developer in the loop.
Handover was the deliverable: repository, documentation, runbook, and credentials. The owner can change the site without us.
SvelteKit · Cloudflare Pages · R2 · D1 · Stripe · Razorpay
04
The system.
One drawing. No screenshots.
05
What we did not build.
Every scope carries an exclusions list.
- No e-commerce. Coating is quoted per job, so a cart would have been a worse version of the enquiry they already run.
- No multi-user roles or approval workflow. One owner edits the site; permissions machinery would have been overhead with nothing to govern.
- No blog or newsletter. Nobody had committed to writing one, and an empty section ages worse than no section.