Retail & product website templates
Five complete websites for selling a physical product, built in Astro 7 and Tailwind 4 — an enamelware shop with a working basket and thirteen product routes, a single-watch house, a hi-fi range, a fragrance house and a florist. Each is a finished site: routed products, a craft or materials page, delivery and returns, and a buying path that matches how the product is actually bought.
Every brand shown is invented and the demos are the templates themselves, running. You buy the source through private GitHub access, change the copy, and deploy it anywhere static. One licence covers unlimited sites, your own or a client's. $49 each, or all 62 templates for $199.
- In this set
- 5
- Each
- $49
- Sites per licence
- Unlimited
- Third-party requests
- 0
The 5 builds
Each is loud in exactly one channel — display type, palette, a moving set-piece, texture or the imagery — and deliberately quiet in the other three. That rule is what stops a set like this reading as one layout in different paint. Click any of them to read the build in full and open the live demo.
KILNMARSH ENAMELWARE
Enamelware homeware store
Loud
Palette
OSMUND
Watchmaker
Loud
Texture
MYRSTAD
Wireless hi-fi / multi-room audio
Loud
Imagery
ORRISHAW
Perfumer / fragrance house
Loud
Display type
WILDROOT
Florist
Loud
Palette
What retail & product sites have to carry
Every build in this set ships all of it. It is the difference between a template that looks finished and one that is.
- 01 A page per product
- Thirteen products across four collections, four fragrances, three finishes. Product routes with their own price, options and stock state — which is what a shop needs and what a one-page product template cannot give you.
- 02 A second browsing axis
- A colour card, a collections layer, a rooms page. Ten fired colourways turn a thirteen-product shop into something that feels like a range, and it is the cheapest inventory you will ever add.
- 03 A materials or craft page
- Where it is made, what is in it, how the case goes from bar to finished part in six operations. In considered product this is the page that carries the price.
- 04 Delivery, returns and care
- Real routes with real copy. Delivery and returns removes the last objection before checkout; a care article is the content customers genuinely read and share.
- 05 A buying path that matches the purchase
- The enamelware build has a working client-side basket with subtotal, delivery threshold and total. The watch and fragrance builds do not — a buy button on a hand-wound watch misrepresents how it is sold. Neither is an oversight.
- 06 A colour system the product produced
- Every enamelware colour is a computed oxide mix over frit white, and the build fails on any hex the mixing engine did not produce. It is why a small range reads as a considered brand rather than a product grid.
What every build includes
- Astro 7 · static output, no client framework
- Tailwind 4 · one @theme block holds the palette
- Content in typed files under src/data
- MDX blog collection, wired to the sitemap
- Self-hosted woff2 — no Google Fonts request
- Zero third-party requests · strict CSP-ready
- Vitest + Playwright suites in the repository
- Designed 404, sitemap, canonicals, per-route meta
- Private GitHub repo access, with updates
Questions
Do any of these take payment?
No. The enamelware build has a real basket — line items, subtotal, delivery threshold, total — but checkout is where you connect Stripe, Polar or a Shopify Storefront API. Hard-wiring one provider into a template dates it within a year and locks you in.
Which one if I have a real catalogue?
The ecommerce build. Twenty-eight routes, thirteen products, four collections, a colour card and a basket — it is the only one here with the machinery. The other four are built for ranges of one to five.
How do I manage stock?
Stock state is a field on each product in typed data. For a small-batch maker that is enough and it keeps the site static and instant. If you need live inventory, the product data is the seam to connect to your source of truth at build time.
I sell one product, not a range.
The watch build is the single-object architecture: product, movement, case, finishes, ownership — everything pointing back at one piece. With a range of twelve you would be fighting it; with one, nothing else in the catalog comes close.
Can I use one template for several client sites?
Yes. The licence is per buyer, not per project — build as many sites as you like, for yourself or for clients. You may not resell the source itself as a template or starter kit.
Other sets
All 62 templates, $199
Every template here plus every future one, delivered as private GitHub repository access with updates. Single templates are $49 each — the 5 on this page alone are $245 bought separately.