[PROJECT NAME]

August 28, 2026 · View on GitHub

Quick Start

bun install
vercel link && vercel env pull
bun dev

Scripts

CommandDescription
bun devDevelopment server
bun run buildProduction build
bun lintRun linter
bun run checkLint, format check, type-aware lint, typecheck, unit tests, manifest and asset checks
bun setup:stylesRegenerate CSS

Tech Stack

Next.js 16, React 19, TypeScript, Tailwind CSS v4, Bun

Project Structure

app/                    # Next.js routes; llms.txt/, agent-content/, sitemap.ts, robots.ts, and manifest.ts (AEO surfaces) live at the app/ root
components/             # UI components (Storybook for the interactive ones)
lib/                    # Everything non-UI
  ├── hooks/           # Custom React hooks
  ├── integrations/    # Third-party services (Sanity, Shopify, HubSpot)
  ├── features/        # Feature flags gating opt-in surfaces (e.g. WebGL)
  ├── webgl/           # 3D graphics (optional, behind lib/features)
  ├── seo/             # Sitemap, robots, and metadata helpers
  ├── utils/           # Pure utilities
  ├── scripts/         # CLI tools
  ├── styles/          # Design system, Tailwind config
  └── dev/             # Debug tools

Content Management

If the Sanity integration is enabled, manage content at sanity.io/manage or through your project's Sanity Studio. Changes publish via webhooks.

Content updates publish through webhooks (Sanity publish, Shopify product/collection updates), which call POST /api/revalidate. To trigger it by hand: curl -X POST "https://[domain]/api/revalidate?secret=$SHOPIFY_REVALIDATION_SECRET" for Shopify tags, or re-publish the document in Sanity Studio. GET is not supported.

Deployment

Vercel deploys automatically on every push to main. If the project isn't linked yet, run vercel link once first (see Quick Start).

Troubleshooting

IssueSolution
Build failsbun install + check env vars
Styles not updatingbun setup:styles + restart
CMS not connectingCheck Sanity env vars + CORS

Built with Satūs by darkroom.engineering