How aiherrera/sveltesaasstarter works
Project Type & Purpose
• Full-stack SaaS template with two “faces”:
– Marketing/Public site (static & SSR pages)
– Authenticated user/admin dashboard
• Backed by Supabase (Auth + Postgres) and Stripe (billing/subscriptions), deployed on Cloudflare.
Main Components
a. Client (Browser or Mobile)
– Loads static / pre-rendered assets (HTML / CSS / JS)
– Performs interactive CSR navigation & form submissions
b. CDN & Edge Layer
– Cloudflare Pages serves static assets
– Cloudflare Workers run SvelteKit SSR & API endpoints
c. SvelteKit App
– File-based routing under src/routes
· (marketing) public pages (pre-rendered where possible)
· (admin) protected pages & API routes (user/dashboard flows)
– lib/ contains shared utilities (e.g., DB helpers)
– config.ts provides site metadata & keys
d. Supabase Services
– Auth (signup/sign-in/forgot-password, JWT sessions)
– Postgres DB (user profiles, subscriptions metadata)
– Exposed via PUBLIC_SUPABASE_URL & keys
e. Stripe
– Payment/Checkout API (checkout sessions, webhooks)
– Billing portal integration (manage subscription, receipts)
f. CI/CD & DevOps
– GitHub Actions (build, lint, test pipelines)
– Deploy hooks to Cloudflare
Architectural Patterns & Principles
• Hybrid SSR/CSR:
– SSR the first load (via Workers) for performance/SEO
– CSR on subsequent navigation (pre-loaded JS)
• Static-first: Pre-render (prerender) marketing pages & blog content
• File-based routing: server versus page modules under src/routes
• Serverless / Edge Functions: each +server.ts / +server.js file becomes an isolated endpoint
• Separation of concerns:
– Public (marketing) and private (admin) route groups
– UI styling via Tailwind + DaisyUI
Essential Elements
– Notes on prerendered vs. server-rendered routes