Docs / Sections
Open documentation actions
Sections
How Better Fullstack groups stack choices across app surfaces, services, tooling, and release paths.
Better Fullstack has many choices, so docs are organized by the part of the generated product they affect. These pages explain what each section means, when to choose an option, and where to find the exact CLI values.
For complete option tables, use Reference Options. For language-specific surfaces, use Ecosystems.
| Section | What it covers |
|---|---|
| Frontend and Apps | Web frontends, React Native apps, app platforms, and frontend-specific constraints. |
| Backend and API | Server frameworks, runtimes, API layers, and multi-ecosystem backend choices. |
| Data and Storage | Databases, ORMs, hosting setup, caching, search, file upload, and file storage. |
| Auth and Payments | Identity providers, auth helpers, OAuth/JWT paths, and payment providers. |
| UI and Experience | CSS, UI libraries, shadcn/ui presets, forms, validation, state, animation, and i18n. |
| AI and Services | AI SDKs, email, realtime, job queues, CMS, analytics, and feature flags. |
| Quality and Tooling | Testing, logging, observability, code quality, docs addons, package managers, AI docs, Git, and install behavior. |
| Deployment | Web/server deployment choices as one stack section, not a top-level docs area. |
Solo and multi mode
In solo mode, one ecosystem drives the visible categories. In Multi-Ecosystem mode, the same concepts become stack parts, such as frontend:typescript:next, backend:go:gin, backend.orm:go:gorm, and database:universal:postgres.