Starter website

Running a shop and want a website? You don’t need this page. Sapt builds and hosts one for you in the app: see Build your website.

This page is for developers who want their own codebase. sample-website is a public, MIT-licensed Next.js starter that already has Sapt wired in: first-party analytics, lead capture, and a booking funnel all light up from a single Project ID. Clone it, point it at your project, rename it, restyle it, and make it the client’s.

Quick start

git clone https://github.com/sapt-ai-org/sample-website.git
cd sample-website
pnpm install

# Point it at your project. This one value is the whole setup.
echo "NEXT_PUBLIC_SAPT_PROJECT_ID=your_project_id" > .env.local

pnpm dev

Grab your Project ID from the Sapt dashboard. That’s the only required value: no SDK, no backend to run, and no API key needed to get the core experience running. The dev server runs on port 2001.

What the Project ID powers

NEXT_PUBLIC_SAPT_PROJECT_ID is the one knob that turns the site live. With just that set, you get:

Feature	What it does
Analytics	The Sapt tracking script records pageviews, clicks, scroll depth and every funnel step. See First-party analytics.
Lead capture	Completed bookings are saved as records of a `booking` type in your Sapt CRM.
Booking funnel	Service, date, time, details, review, confirm.

Create the booking record type in your project first, or bookings can’t save. The repo’s SAPT_SETUP_GUIDE.md has the schema.

Optional: CMS content

Add an API key to pull section copy from the Sapt CMS instead of hardcoding it:

SAPT_API_KEY=sapt_your_api_key   # server-side reads for CMS content

Then set useCmsContent: true in src/config/site-config.ts. With the key and the flag set, non-developers can update the site’s copy from the Sapt dashboard. Leave them out and the site runs on its built-in copy.

Customizing

Knob	Where
Site content	`src/config/site-config.ts`: company name, tagline, phone, hero copy, and the `theme` and `useCmsContent` flags.
Brand colors	The `@theme` block in `src/app/globals.css`.
Worker name (per client)	`wrangler.jsonc` defaults the deploy name to `sample-website`. Rename it per client before you deploy.
Styling	Standard Next.js + Tailwind. Restyle freely; it’s your repo.

Start with the API

Platform

Social publishing

Analytics

REST API guides

MCP connector

Starter website

Quick start

What the Project ID powers

Optional: CMS content

Customizing

Keep going

First-party analytics

CMS

Onboarding funnels

​Quick start

​What the Project ID powers

​Optional: CMS content

​Customizing

​Keep going

First-party analytics

CMS

Onboarding funnels

Quick start

What the Project ID powers

Optional: CMS content

Customizing

Keep going