Platform architecture
How BravoBlock marketing, waitlist, and admin surfaces fit together
BravoBlock pairs a conversion-focused public experience with a waitlist engine and an administrative back office.
Public experience
The main web app presents the product story and waitlist capture. Sign-ups flow into the shared subscriber store for review and engagement.
Waitlist engine
The waitlist path validates submissions and persists them for operators. Lifecycle signals (approval, rejection, messaging) are coordinated from admin modules documented under Administrative tools.
Admin surfaces
| Module | Docs |
|---|---|
| Overview | Administrative tools |
| Messaging | Email campaigns |
| Audience | Subscriber management |
Technology snapshot
- App framework: Next.js App Router
- UI system: shared
@bvb/uidesign tokens and primitives - Data: Supabase PostgreSQL with typed application access
- Docs site: this static Fumadocs export (
bvb-docs)
Related reading
- Getting started — practical first steps
- Welcome — full documentation map
Tip
When you are ready to operate the list, open Subscriber management and Email campaigns side by side in the sidebar.