This starter provides a focused Next.js foundation. Add product-specific services only after their requirements are documented in product/.
For the exact dependency versions and package metadata, read ../package.json.
| Technology | Why it is included | Entry point |
|---|---|---|
| Bun | Package manager and script runner. | package.json |
| Next.js | Application framework with the App Router. | next.config.ts, src/app/ |
| React | UI rendering layer. The React Compiler is enabled. | next.config.ts |
| TypeScript | Strict, typed application code. | tsconfig.json |
| Tailwind CSS | Utility-first styling. | src/app/globals.css, postcss.config.mjs |
| shadcn/ui and Base UI | Accessible, composable UI primitives. | components.json, src/components/ui/ |
| Tabler Icons | Icon library configured for shadcn/ui. | components.json |
| next-intl | Locale-aware routing and translations. English (en) and Spanish (es) are configured; English is the default, and application routes live below src/app/[locale]/. |
src/i18n/routing.ts, src/i18n/request.ts, src/i18n/navigation.ts, src/proxy.ts, src/app/[locale]/, next.config.ts |
| next-themes | Theme switching support. | src/components/theme-provider.tsx |
| @dnd-kit | Drag-and-drop interactions for canvas elements and slide reordering. | src/features/presentations/components/slide-renderer.tsx, src/features/presentations/components/slide-sidebar.tsx |
| Zustand | Per-editor client state for the session snapshot, active slide, selection, and drafts. | src/features/presentations/components/editor-store.ts, src/features/presentations/components/editor-store-provider.tsx |
| Biome | Formatting, linting, and import organization. | biome.json |
@/*resolves tosrc/*.- shadcn/ui components use
src/components/ui/; its aliases are defined incomponents.json. - Tailwind styles start in
src/app/globals.css. - The default scripts are
bun dev,bun lint,bun format,bun build, andbun start.
The package manifest does not include an authentication provider, database client, ORM, or billing integration. Choose and document those only when the product requires them.
When you add an important library or platform service, document its purpose and configuration entry point here. Keep product behavior and business decisions in product/, not in this stack reference.