Maison Terracotta — Fashion Boutique Website (Frontend + Backend)

Eight pages, a real product catalog, and real Stripe checkout — this is a DYNAMIC website with a genuine e-commerce backend, not a static template with a payment-link placeholder. 1. Home (index.html) — hero, featured products pulled live from your catalog. 2. Collection (collection.html) — the full catalog with client-side category filters. 3. Product Detail (product.html?slug=...) — one product, "Buy Now" -> Stripe Checkout. 4. Our Story (story.html), Lookbook (lookbook.html), Journal (journal.html), Shipping & Returns (shipping-returns.html) — static editorial pages. 5. Contact (contact.html) — enquiry form, stored in your database. WHOSE DATABASE, WHOSE STRIPE ACCOUNT. Yours, not this platform's. Before anything here does something real: 1. Create a Postgres database anywhere you like — Vercel Postgres, Supabase, Neon, or your own server, since the backend just speaks the standard Postgres wire protocol. 2. Run schema.sql against it once to create the products/orders/ contact_submissions tables. 3. Create your own Stripe account (or use an existing one) and, in your Vercel project's Settings -> Environment Variables, set: DATABASE_URL your database connection string PRODUCTS_ADMIN_KEY any secret string you choose STRIPE_SECRET_KEY from your Stripe Dashboard STRIPE_WEBHOOK_SECRET from Stripe Dashboard -> Developers -> Webhooks, after adding an endpoint pointing at https://<your-site>.vercel.app/api/webhooks/stripe listening for checkout.session.completed This platform only ships the code that talks to whichever database and Stripe account you connect — it never provisions, stores, or has access to either. ADDING PRODUCTS. Once published, this purchase's library page shows a "Manage live data" panel — paste in your PRODUCTS_ADMIN_KEY and you can add new products (name, price, category, image URL, description) and delete existing ones directly against your live site, no redeploy needed. Editing an existing product's price or image today means re-adding it with the same name (upserts by slug) — a dedicated edit form is a natural next step, not built yet. PREVIEW LIMITATION. Every dynamic section (featured products, the full catalog, product detail, checkout, the contact form) calls a real endpoint that only exists once deployed — this platform's own preview has no backend to call, so each shows a friendly "try it once deployed" message here. That's expected, not a bug. CUSTOMIZATION. The frontend pages (copy, styling) work the same way as this platform's other website templates — describe a change and regenerate. The backend files (api/products.ts, api/create-checkout-session.ts, api/webhooks/stripe.ts, api/contact.ts, package.json, schema.sql) ship as-is; they aren't run through the AI editor. SCOPE NOTE. This template was adapted from a much larger brief that asked for a full multi-tenant CMS platform (a generic Business/Website/Page/ Section database, a role-based admin dashboard, dynamic categories, custom domains). That's a different system than a single purchased template — this delivers the legitimate e-commerce core (real product catalog, real checkout, real order and enquiry storage) within this platform's actual DYNAMIC_WEB_TEMPLATE architecture instead.