CodeNXT Lab · Case study 02 / Starcolours Coating
Starcolours Coating.
Marketing site with a self-serve dashboard. The owner edits the everyday content: images, prices and copy.
Visit star-colours-coating.pages.dev →
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 to never have 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.
- The site had to run on their own accounts, so leaving us would not mean losing it.
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. The everyday content, meaning images, prices and copy, is an entry the owner can change, with no build step and no developer in the loop.
The site runs on the owner’s own Cloudflare, domain and email accounts. They did not buy the code. It is licensed from us, and the site keeps running if they ever leave.
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.