Skip to main content

Features

This starter is built around a Strapi-managed page builder, reusable AI skills, and a typed Next.js UI. It gives teams a working foundation for content, rendering, auth, media, workflow, and docs before project-specific features begin.

Stack​

AppStackEntry
apps/strapiStrapi 5, PostgreSQL through Docker or SQLiteapps/strapi/src/index.ts
apps/uiNext.js 16 App Router, React 19, Better Auth, next-intl, TailwindCSS v4apps/ui/src/app/[locale]/layout.tsx
apps/docsDocusaurus 3apps/docs/docusaurus.config.ts

Shared code lives in packages/*.

Content And Page Builder​

  • Editable pages — editors compose pages from Strapi dynamic-zone components.
  • Typed rendering — React components receive typed Strapi component data through @repo/strapi-types.
  • Component registry — Strapi component UIDs map to UI components in one predictable place.
  • Smart population — small per-component populate configs are combined automatically.
  • Page hierarchy — full paths, parent/child pages, breadcrumbs, and redirects are handled in Strapi.
  • Seed data — baseline pages, navbar, footer, and demo content can be shared with the team.
  • Add content type workflow — extend Strapi schemas, regenerate types, and render new data in the UI.

UI​

  • App Router UI — localized Next.js routes render Strapi-managed pages.
  • Static and dynamic Strapi pages — built-in routes cover static pages, dynamic Strapi pages, auth pages, and development overview pages.
  • Strapi API clients — typed server and browser-safe clients fetch public and private content.
  • Built-in API routes — route handlers cover auth, Strapi proxying, preview, assets, and health checks.
  • Preview support — editors can open draft or published content from Strapi.
  • Caching defaults — Strapi responses cache, Next.js page cache, ISR, and static export tradeoffs are documented.
  • Cache revalidation — Strapi publish/update/delete events can invalidate affected Next.js paths and shared data tags.
  • CDN cache purge — optional operator-triggered CDN eviction is available for urgent cache updates.
  • Next proxies — controlled proxy middleware handles locale redirects, HTTPS redirects, Strapi-defined redirects, basic auth, and auth guards.
  • SEO helpers — metadata, sitemap, robots, canonical URLs, and structured data are generated from content.
  • Image handling — Strapi media helpers and optional imgproxy support are included.
  • Environment variables — runtime config, CSR env injection, public variables, and debug flags are documented.
  • Error handling — React error boundaries and Sentry integration are covered.
  • Next configuration — Next.js output modes, React Compiler, Sentry wrapping, and image configuration are documented.

Strapi​

  • Local setup — PostgreSQL runs through Docker for development.
  • Schema conventions — content types, components, relations, lifecycle hooks, and document middlewares are documented.
  • Generated Strapi types — schema-generated types are shared with the UI.
  • CMS redirects — editors manage source → destination redirects as content; the UI proxy applies them, and page moves create them automatically.
  • Rich text editors — CKEditor and Tiptap editor integrations are documented.
  • Upload providers — local storage, Azure Blob Storage, and AWS S3 are supported.
  • Email providers — Mailgun production email and Mailtrap development email are wired through Strapi provider config.
  • Preview — Strapi preview is configured for draft/live editorial review.
  • Users & Permissions — Strapi end-user accounts and JWT behavior are documented.
  • Config Sync — admin configuration can be exported and synchronized between environments.
  • Cron jobs — scheduled work and multi-replica deployment concerns are documented.
  • Docker build — container build guidance is available for Strapi deployments.

Authentication​

  • End-user auth — Better Auth owns the session cookie in the UI.
  • Strapi JWT — Users & Permissions issues the JWT used for per-user Strapi calls.
  • OAuth providers — social providers use the same Better Auth + Strapi bridge.
  • Admin SSO — Strapi admin Microsoft SSO is documented separately from end-user auth.

Development Workflow​

  • Monorepo scripts — Turbo runs app and package tasks from the root.
  • AI skills and workflows — agent-ready skills cover common tasks such as starting work, adding page-builder sections, writing tests, reviewing changes, and opening PRs.
  • Shared packages — design tokens, path helpers, generated Strapi types, lint config, TypeScript config, and release config live in packages/*.
  • Code quality — ESLint, Prettier, Lefthook, Commitizen, and Conventional Commits are included.
  • Internationalization — UI messages and Strapi content locales are documented together.
  • Testing and QA — Vitest, Playwright, axe, visual tests, SEO checks, and Lighthouse CI are covered.
  • Deployment — GitHub Actions, Heroku, Vercel, and Docker deployment notes are documented.
  • Design system — shared tokens, typography, rich text styling, and CMS component design rules are documented.
  • Integrations — Observability (structured logging, Azure Monitor, Sentry), reCAPTCHA, and CDN / Azure Front Door setup have dedicated reference pages.