01
A catalog that feels curated.
Releases are presented as a body of work, with enough context on each card to make browsing feel intentional rather than like scrolling an upload list.
ZilalWorksStorefront buildA storefront the artist runs.
The music already had a world. The storefront gives it a system: a catalog that feels curated, a direct path to purchase, and a back end the artist runs himself.
- Client · Pre-launch
- Music storefront
- Astro + Stripe
The problem
ZilalWorks wanted to sell music directly to listeners with a strong identity, not a generic store template, and the freedom to add releases, take payments and deliver files without a developer.
02
Every track carries its context.
Track pages keep listening, the story behind the track, licensing and related releases together, so a listener can buy with confidence.
03
A direct path to purchase.
A custom cart keeps the storefront's look, then hands payment to Stripe Checkout only when the listener is ready. Each order is recorded, and the customer gets an email with a protected download link.
04
The catalog changes without code.
Releases, artwork, pricing, audio and homepage content are edited in Decap CMS, with a live preview, and the public site rebuilds from it.
How it was built
Astro, Decap CMS, Stripe Checkout, Supabase and Resend.
- Protected downloads, so files only reach people who paid
- Built and ready; it launches once the artist finishes the final content
- Site
- Astro
- Catalog
- Decap CMS
- Payments
- Stripe Checkout
- Data
- Supabase
- Resend
What happens when someone buys
- A listener buys a track
- Stripe takes the payment
- The download unlocks for that buyer
- The link arrives by email
Want work like this for your business?
A few questions, or just call. Either way, you're talking to me.