Sheltüh

A Melbourne-first curated creative events discovery and ticketing marketplace.

• Stack:
  • Next.js 16 (App Router) + TypeScript + Tailwind CSS v4, hosted on Vercel.
  • Supabase: Postgres for data, Auth for accounts.
  • Stripe Connect Express for payments and organiser payouts.
  • Leaflet with Esri tiles for the map.
• Status: feature-complete for the MVP flows below and tested against real Postgres, but not deployed yet. See docs/supabase-setup.md for the go-live steps.
• More:
  • docs/architecture.md: data model, API and payment flow.
  • docs/PROJECT_CONTEXT.md: business, legal and roadmap context.

What's built

Public, no account needed:

• /: curated event feed with category, date and free/paid filters.
• /map: Scene Map.
• /events/[slug]: event details and guest checkout. Free tickets are issued instantly; paid tickets are paid for on /checkout/pay, in Stripe's embedded checkout form.
• /checkout/success: order confirmation with ticket codes, also emailed to the buyer. An oversold order is refunded automatically.

Accounts: /signup, /verify, /login, /forgot-password.

Organisers (need an admin-approved application):

• /organisers/apply: apply, see your status, and edit and resubmit if rejected.
• /dashboard: event drafts, an optional event photo, ticket types with a live fee preview, and submitting for review.
• /dashboard/payouts: Stripe Connect onboarding.

Admins: /admin/organisers and /admin/events are review queues (approve, reject with a reason, unpublish).

Run it locally

Demo mode (no setup, sample data only):

npm install
npm run dev

Live mode: copy .env.example to .env.local and fill it in from your Supabase project and Stripe test account (see docs/supabase-setup.md). With the Supabase variables set, the app uses the real API; without them, it falls back to demo mode.

Commands

npm run dev            # dev server
npm run build          # typecheck + production build
npm run lint           # eslint
npm test               # unit + API tests (API tests run against in-process Postgres)
npm run test:e2e       # Playwright browser tests
npm run test:journey   # opt-in end-to-end journeys over HTTP (JOURNEY=1 + TEST_DATABASE_URL; docs/testing.md)
npm run promote-admin -- [email protected]   # grant admin (needs SUPABASE_SECRET_KEY)
npm run seed-dev-data  # load sample events into a dev database

TEST_DATABASE_URL=postgres://user@host:port/db npm test runs the API tests against a real Postgres server through the production driver instead of PGlite. Each test file creates its own throwaway database.

What each test layer covers, and the checks that still need a person (Stripe test mode, real email, real phones): docs/testing.md.

Layout

app/                 pages, plus app/api/** route handlers
components/          UI
lib/api/             browser client for the API
lib/auth/            Supabase Auth in the browser
lib/server/          API logic: handlers, validation, SQL, wiring
supabase/migrations/ database schema — apply in filename order
scripts/             admin promotion, dev seed data
tests/, e2e/         vitest (incl. tests/server API tests), Playwright

Not built yet

• QR check-in.
• Venue coordinates.
• "Who's Going".