Blank frontend shell

Build every salepage from the business PRD.

This starter keeps the backend, admin, checkout, database, and API contracts ready. The active frontend is intentionally blank so each project can receive a purpose-built salepage design.

Backend/admin retained
Frontend demo removed
Database contract ready

Project blueprint

salepage00 starter

Ready
FrontendBlank shellWaiting for PRD
Adapterblank-starterActive
BackendAdmin templateProtected
DatabasePostgres contractConfigured by env

import { createOrder } from "@/frontend/api";

await createOrder(projectCheckoutPayload);

// Order appears in admin dashboard

Implementation workflow

Read before writing frontend code.

Keep the template safe: custom UI belongs in the project frontend; reusable business-agnostic behavior belongs in the backend template.

Step 01

PRD first

Complete the project PRD before writing a salepage layout or copy.

Step 02

Fresh frontend

Build the salepage UI for the real business instead of patching old demo sections.

Step 03

Plug contracts

Connect lead, order, tracking, settings, coupon, and upload helpers.

Step 04

Verify admin

Confirm checkout, orders, leads, admin settings, and deployment readiness.

Contract-first plug point.

New salepage screens should call helpers from `src/frontend/api`. The backend/admin surface stays stable while each business gets a custom frontend.

POST /api/leads
POST /api/order
POST /api/track
GET /api/settings
GET /api/settings/pixel
POST /api/upload-slip

Starter docs map

These files are the handoff protocol for the next frontend implementation sprint.

docs/salepage-prd-template.md
docs/frontend-backend-contract.md
docs/frontend-implementation-checklist.md
docs/env-database-guide.md