B2B SaaS Dashboard
Build an authenticated product UI with fast docs/marketing routes and interactive account features.
- public marketing routes stay fast
- private dashboard ships only needed JS
- auth and data models evolve safely
Include
Can Skip
Planning Guide
Start with the smallest setup that solves the problem. Add backend and orchestration options when your product needs them.
Build an authenticated product UI with fast docs/marketing routes and interactive account features.
Include
Can Skip
Ship admin tools for support, billing, and reporting with stronger backend boundaries.
Include
Can Skip
Run docs, changelog, and blog content with optional light interactivity and theme controls.
Include
Can Skip
Launch quickly with minimal moving pieces, then progressively enable backend and orchestration when needed.
Include
Can Skip
Scale a product with strict auth boundaries, richer APIs, and reproducible full-stack environments.
Include
Can Skip
Keep what helps now. Skip what adds complexity you do not need yet.
Include when: You want fast first paint and mostly static routes.
Skip when: You need a pure SPA with client-side routing everywhere.
Include when: You have interactive widgets or forms in isolated spots.
Skip when: Your pages are static and only need server-rendered HTML.
Include when: You want speed and consistent utility-driven styling.
Skip when: Your team already has an established component CSS system.
Include when: Multiple apps or themes need one shared visual language.
Skip when: Single throwaway prototype with no long-term design reuse.
Include when: Users need sign in, sessions, roles, or OAuth providers.
Skip when: Public-only marketing/docs with no protected user flows.
Include when: Type-safe SQL and migrations are part of the frontend app.
Skip when: Your backend owns all data access behind APIs already.
Include when: You need domain-heavy APIs, background jobs, or strict layering.
Skip when: Frontend-only site or lightweight API needs only in Astro endpoints.
Include when: You run multiple local services and want one-command orchestration.
Skip when: Single-process app without service orchestration complexity.
Include when: You want reproducible local/CI environments across machines.
Skip when: Team is fully local-native and infra parity is not a concern yet.