Practical base
Core + Admin
The workspace generator keeps Admin governance enabled for platform auth and RBAC even when the admin UI surface is not selected.
Internal developer handbook
Understand the platform fast, without flattening how it actually works.
BrightWeb is a shared platform monorepo for scaffolding and evolving client apps with a modular database and shared domain packages. The practical base is Core + Admin. Optional modules such as CRM and Projects extend schema and domain behavior, but they do not usually install a ready-made frontend product UI into client apps.
Optional modules
CRM, Projects
Optional modules primarily extend schema, shared logic, package helpers, and light starter wiring.
Database model
Modular + forward-only
Client stacks resolve module order from the registry, then materialize an installable Supabase workdir.
Quick links
Main docs sections
Understand the practical base
Core + Admin is the real install floor for platform auth, governance, and RBAC.
See what modules really ship
CRM and Projects are mainly schema, domain logic, contracts, and light starter wiring.
Check dependency order
CRM requires Admin. Projects requires CRM. The docs show the resolved install chains.
Run the database flow correctly
Plan, materialize, and upgrade client stacks without inventing unsupported migration behavior.
Current model
How to read BrightWeb today
- Use the repo as the source of truth: generator behavior, module SQL, and shared package exports.
- Do not assume optional modules install a finished frontend product UI for client apps.
- Treat client app UI as owned by the client application, built on top of shared contracts and domain behavior.
Next actions
Use the docs in this order
- Read Getting Started to understand what `create:client` generates.
- Read Platform Base before deciding what “base only” really means.
- Use Modules and Dependency Resolution before enabling CRM or Projects.
- Use Database Flow and Recipes before touching client stacks or migrations.