BootRoom
Private, invite-only league management platform for 5-a-side to 7-a-side football leagues. Members can view match history, league tables, and player statistics. Admins can manage invites, add games, and control which features are enabled for their league.
Domain
Everything lives on craft-football.com — public marketing pages, public league pages, and the authenticated member app. m.craft-football.com permanently redirects here.
How login works
Authentication is handled by Supabase (email + password and magic links).
- New users must be invited via an invite link generated by an admin
- On sign-in, users are redirected to their intended destination
- Auth-gated routes are protected by middleware — unauthenticated users are redirected to
/sign-in
- Users with a Supabase account but no profile row are redirected to
/profile-required
Access tiers
| Tier | Who | Access |
|---|
| Admin | League creators and invited admins | All features + settings + feature flag controls |
| Member | Invited members | Features the admin has enabled for members |
| Public | Anyone with the public league link | Features the admin has enabled for public |
Tech stack
- Next.js 14 (App Router) — TypeScript, strict mode
- Tailwind CSS v3 — dark-mode-first, slate palette
- Radix UI — unstyled primitives for accessible components
- Supabase — Auth + PostgreSQL + Row-Level Security
- Vercel — deployment
Repository layout
app/app/ — authenticated member routes (league, players, settings)
app/api/ — API routes (auth, league, invites, features)
components/ — shared UI components
components/ui/ — base UI primitives (button, input, navbar…)
lib/ — types, utilities, data access, feature helpers
supabase/migrations/ — database migration files (run in order)
scripts/ — data migration and automation scripts
Getting started
See SUPABASE_SETUP.md for Supabase project setup and DEPLOY.md for Vercel deployment steps.
npm install
npm run dev
# Open http://localhost:3000
Working rules
- All new features are built behind an admin-controlled feature flag
- Features start hidden from members and public — admins always see everything
- Promote to members by toggling enabled on; promote to public by toggling public_enabled on
- Each tier can have independent config (e.g. different visible stat columns for public vs members)
- See docs/FEATURE_FLAGS.md for the full development standard
