niche, services, hours, proof
SYSTEM 02 / SITESBUILDER PREVIEW MAKING
SitesBuilder Preview Factory Full-Stack Flow
A business brief becomes structured content, assets, Astro route code, built static HTML, Vercel deployment, and a public preview URL used only as display/proof.
Control plane + data plane + trust boundaries
Repo audit: Astro static app, preview data model in src/data/previews.ts, preview pages under /preview and /zh/preview, Vercel deployment to sitesbuilder.store.
photos, menu, map, tone
src/data/previews.ts
preview slug + components
theme CSS, responsive sections
astro check + astro build
deployed HTML/CSS/assets
customer-facing display route
screenshots, links, overflow, pixels
- 1. Intake
Collect the business facts that customers need: services, prices, location, proof, media, contact paths.
- 2. Normalize
Convert messy facts into repeatable structured data and section decisions.
- 3. Render
Astro components combine content, assets, copy, and theme CSS into a responsive static route.
- 4. Ship
Vercel serves the built route from sitesbuilder.store; QA checks the actual public display output.
brief / research→structured preview schema→Astro props
photos / generated crops→public assets + CSS treatment→route sections
Astro build→Vercel deployment→sitesbuilder.store URL
Content boundary
Raw notes are internal; the public route only shows customer-facing facts and flow.
Build boundary
Static Astro output means no runtime backend is needed for the preview display.
QA boundary
A route is not accepted until links, mobile layout, overflow, and image pixels are checked.