Content pipeline
Use Strapi for pages, pricing data, editorial content, and API delivery while keeping the site shell in Next.js.
Next.js 16.1.6 / Strapi 5.38.0 / Bun
The frontend is ready in Next.js, the CMS is ready in Strapi, and both live in one Bun workspace so the project can grow without reworking the foundation.
Local endpoints
Frontend
http://localhost:3000
CMS
http://cms:1337
Admin
http://cms:1337/admin
Use Strapi for pages, pricing data, editorial content, and API delivery while keeping the site shell in Next.js.
Run both apps with one command and keep the frontend and CMS in the same workspace from day one.
The starter is intentionally lean so domain models, public pages, and integrations can be added without cleanup first.
First steps
Start both apps
bun run devOpen the CMS
http://localhost:1337/adminPoint the frontend at Strapi
apps/web/.env.localFrontend
Next.js 16.1.6
App Router, TypeScript, Tailwind CSS 4, ESLint
CMS
Strapi 5.38.0
TypeScript, SQLite, admin panel at /admin
Workspace
Bun 1.3.0
Single lockfile, shared scripts, one repo