Tally
One multi-event platform (Next.js + Supabase) for running live events: public event pages, registration, the participant area, check-in and scanners, seating, agenda, logistics, messages, lucky draw, live voting, stage screens, and booth sales.
Where to read
| Document | What it is |
|---|
docs/PRODUCT.md | What the platform does today: every module, who uses it, what the organiser sets in the CMS, and what was decided against. |
docs/STATUS.md | What is in flight, what waits on whom, parked Lows. Updated by every PR. |
DESIGN.md | UI source of truth: palette, type, motion, components. |
CLAUDE.md | Rules for every coding agent (and a good summary for humans): production safety, data rules, roles, language. |
docs/ops/cron.md | Scheduled jobs (pg_cron and the external cron) and how to check them. |
docs/GLOSSARY.md | Indonesian words in paths and identifiers, with their English meaning, and the naming rules for new code. |
History lives in git log and PR descriptions.
Local development
Requires Node.js 22 (the check script uses --experimental-strip-types) and npm.
npm ci
cp .env.example .env.local # fill in local values only
npm run dev
Never point a local run at the production database. Use the Supabase local stack (the repo has no supabase/config.toml, so run supabase init once, then supabase start; the migrations need pg_cron, pg_net, Vault and the Supabase roles, so plain Postgres won't run them all) or a fake PostgREST, and stub every email and WhatsApp sender. See "Running locally" in CLAUDE.md.
Environment variables are listed in .env.example. The Supabase ones are read through src/lib/env.ts: NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY and SUPABASE_SERVICE_ROLE_KEY (server only, never in browser code).
Editor and agent tool config with environment-specific values (.mcp.json, .vscode/) is git-ignored: keep your own copy locally.
Checks before a PR
CI (.github/workflows/ci.yml) runs the same four on every pull request and on main.
npm run typecheck
npm run check
npm run lint
npm run build
URL shape
/login, then /events (event picker). /users is workspace-wide./e/<slug> is the public event page (/e/<slug>/en, /e/<slug>/id for other languages). Other event-scoped pages are /e/<slug>/<page>, which src/proxy.ts rewrites to /<page>?eventSlug=<slug>.- Admin is
/e/<slug>/admin/.... Participant, staff and stage screens are listed per module in docs/PRODUCT.md.
