WHOA.
How it's built

Site Concept

Everything spirals out from one home page — customer-facing journeys curl one way, the shared backend portal curls the other. One account model, one login, every side of WHOA connected underneath it.

FrontendBackend
1Shop The WHOADEGA2Music Collective3Art Collective4Event Calendar5Brand Ambassadors6WHOA Games7Same Same But WHOA8WHOA POS1Login / Portal2Customer Tab3Brand Ambassador Tab4Art & Music Tabs5Event Sales Tab6Admin Tools7Super Admin8IntegrationsWHOAHome

Frontend journeys

  1. 1Shop The WHOADEGASquare-powered storefront — browse, cart, checkout.
  2. 2Music CollectiveMeet the DJs & producers behind WHOA Wednesday.
  3. 3Art CollectiveIndependent artists — shop their work directly.
  4. 4Event CalendarFlyer archive, RSVP/tickets, and the live calendar.
  5. 5Brand AmbassadorsReferral program landing page — apply to join.
  6. 6WHOA GamesSnake, puzzle, graffiti wall, scavenger hunt & more.
  7. 7Same Same But WHOAA psychedelic point-and-click adventure.
  8. 8WHOA POSThe in-person register staff use at events & pop-ups.

Backend journeys

  1. 1Login / PortalOne account for every role — customer, artist, staff.
  2. 2Customer TabReal Square purchase history, matched by email.
  3. 3Brand Ambassador TabReferral code, trackable links, payouts, commissions.
  4. 4Art & Music TabsSelf-service profiles — bio, links, product submissions.
  5. 5Event Sales TabSell For Us crew — sign up to work events, see your schedule.
  6. 6Admin ToolsEvents Admin & Art Admin — review and approve submissions.
  7. 7Super AdminGrants every permission; the only way to unlock a tab.
  8. 8IntegrationsSquare (catalog & payments), Supabase (data), Resend (email).

How it fits together

Every page — frontend or backend — is the same Next.js app talking to the same three outside services: Square holds the real product catalog, inventory, and takes payments (online and at the in-person register); Supabase is the database behind every account, permission, RSVP, and submission; Resend sends every confirmation and staff notification — including the one-click Approve/Decline buttons that let staff review an application right from their inbox.

The account model is what ties both spirals together: everyone — a customer, an ambassador, an artist, a musician, event sales crew, or a Super Admin — is the same kind of row in the same table, logged in through the same door. What's different is only which tabs a Super Admin has unlocked. Apply for something on the frontend (Brand Ambassador, Sell For Us, Art or Music Collective) and, once approved, the matching tab just appears the next time that account logs in.