WGA Raid Hub
A live web app for We Go Again raid teams -- a full raid hub giving raiders a personal profile and officers a complete management dashboard. Supabase (Postgres + Auth + RLS) is the backend; there is no build step and no server of its own -- both pages are static HTML/JS hosted on GitHub Pages, talking to Supabase directly from the browser.
Supports multiple teams (Phoenix, Hellfire Rollers, Immolation) from a single codebase. Append ?team=hellfire (or ?team=immolation) to any URL to switch teams; a raider or officer who's claimed a character on a given team is redirected there automatically on a cold visit.
What it does
Guild page (public, guild.html)
The one page that is not scoped to a raid team: the guild above the three teams, rather than any one of them. It is where a visitor who does not know which team they want starts.
Carries the team cards (badged with your own team, plus a signup link for any team whose signups are open), guild-wide Twitch streams (whoever is live gets an embed, everyone else a compact row), a three-headline news teaser, a BoE Sales nav link to the BoE page, About the Guild, and the guild's external links. Built across milestone #27.
It replaced the cold-landing team-picker modal on index.html, so a visitor with no ?team= in the URL now lands here instead of on a three-button prompt. A signed-in raider with exactly one claimed team still goes straight to that team's roster, so nobody's daily path got longer. index.html keeps its URL and stays the team page; whether the guild page should become the site's front door is tracked in #794.
BoE Sales (boe.html)
Report a find and follow what happens to it, on one page. The report form sits at the top (#891, moved off index.html's BoE tab; no login needed, and it picks its own reporting team), and under it the found-BoE auction lifecycle (#864): record listings and sales (payout split computed from the guild-wide policy), mark payouts paid, retire dead items, undo any of those; a summary strip of guild income, outstanding payouts, and finds per team. Guild-wide, not per-team: BoEs are guild property, so a BoE manager or site admin sees every team's finds in one list with the finding team named per row. Open to anyone signed in (#890) and scoped by the read policies: a team officer sees the teams they staff and settles those payouts (#888), a raider sees the finds reported under their own character (#889) with no buttons. Reached from the BoE Sales link in every page's nav, none of them access-gated any more; index.html?team=<slug>#boe and guild.html#boe redirect here, the first carrying its team. Signed-out visitors get the form and a sign-in prompt in place of the records.
Landing page (public, index.html)
- Character selector dropdown -- choose your character to open your profile (officers get the full roster; a claimed-but-unclaimed-dropdown raider gets a one-click "View My Profile" instead)
- Stats row showing current Raiders count and total items distributed this season
- Recent Loot feed, searchable, showing items distributed across the roster this season
- Raid Progression tracker -- every raid in the current season as cards with kill counts, boss lists, first-kill dates, and AOTC badge
- A floating live Twitch widget for raiders currently streaming
- Discord login -- sign in with Discord (via Supabase Auth) to claim your character and unlock personalised features
Other public nav tabs: Roster (current + next-season "tentative" roster), Streams (full streamer directory), Sign Up (multi-step season signup form), History (past seasons' progression and rosters), About (team bios, guild leadership bios, guild info, contact form), News, Help. The current view (and an open profile) is reflected into the URL, so a reload restores where you were instead of always dropping back to Home.
Raider profile (public, no login required to view)
- Attendance -- season attendance percentage with a colour-coded progress bar and monthly sparkline, expandable to show Excused/No Show dates
- Items Received -- items received this season, expandable to the full list with slot and difficulty
- BiS List -- link to the player's submitted BiS list; submit or update directly from the profile when submissions are open
- Wishlist -- per-item tiered status (BiS / Good / OK / Catalyst Only / Pass) a raider sets themselves, feeding into priority generation
- Loot Priority -- every BiS item with the player's current priority rank, slot, and source
- Self-mark received -- submit items received outside of raid (M+, Great Vault, Crafted, Catalyst, Bonus Roll) for officer approval; a Discord-authenticated raider marking their own claimed character is auto-approved
- M+ Exclusion request, when the team has that window open
- Trial / Bench / Backup Tank / Backup Healer badges, when applicable
Discord login (raiders and officers)
Everyone signs in with the same Discord button (Supabase Auth, full-page redirect). On first login a raider claims their character from the team's roster; a persistent "Claim your character" prompt on the landing page covers logging in without a claim yet, including pointing at the right team if they're already claimed elsewhere. Officer/admin status is derived from the database (team_members.role, a site_admin grant in guild_grants), not a separate login -- an existing Discord session just unlocks more once it resolves.
- My Profile -- nav dropdown shortcut to your claimed character's profile
- Officer Access -- shown to officers/team leaders/site admins, links straight to
officer.html
- Site Admin -- a separate Discord-authenticated page (
admin.html), gated to site admins only (a site_admin row in guild_grants)
Officer dashboard (officer.html)
Discord-authenticated, session lasts 2 hours. A global season selector filters loot, fairness, and attendance to a specific past season. Every tab/sub-tab below can be individually hidden per team via Feature Flags (Admin tab), except Roster and Season Settings.
| Tab | Sub-tabs | What it shows |
|---|
| Roster | Roster / Discord Claims | Roster: full player table with attendance, items, BiS status, Trial/Bench/Backup Tank/Backup Healer tags; filter and sort; click a player to expand their profile inline with edit controls, add/remove/rename players. Discord Claims: every claimed Discord-to-character mapping; remove a claim or grant/revoke officer access. |
| Loot | Import / Import History / Loot Fairness | Import: paste RCLootCouncil JSON to write loot to the database. Import History: view previously imported batches. Loot Fairness: bar chart of items received per player, filterable by Heroic or Mythic. |
| Priority | Priority List / Contested Items / Unmanaged Items | RCLootCouncil export string generator. Priority List: full priority order per item, filterable/searchable, each item has a Priority Generator button (auto-rank by blended score) with an editable, saveable order. Contested Items: every item sorted by how many players have it on their BiS/Wishlist. Unmanaged Items: BiS items with no priority order yet, badge-counted. |
| BiS Manager | Submissions / BiS Lists | Submissions: open/close BiS submissions globally or per player; approve or reject submitted links. BiS Lists: role-grouped player table with each raider's wishlist BiS count and an Incomplete Wishlists badge. |
| Attendance | Manage / Attendance Scores / Bench Fairness | Manage: attendance grid editable per player per night, Refresh from WCL, Commit Attendance Scores. Attendance Scores: players below a threshold. Bench Fairness: bench player attendance comparison. |
| Scoring | -- | Fetches WarcraftLogs performance scores per player, editable/overridable manually, committed as one of the Priority Generator's blended-score inputs. |
| Signups | Signups / Pending Roster / History | Signups: open/close the public form; review/approve/deny submissions. Pending Roster: approved applicants awaiting a roster add, with Trial/Backup Tank/Backup Healer toggles at promotion time. History: past signup activity. |
| M+ Exclusions | -- | Review/approve/reject raider-submitted M+ exclusion requests; toggle exclusion per player manually; open/close the request window. |
| Received Item Requests | -- | Approve or reject raider self-mark requests; writes straight to loot history on approval. |
Site Admin dashboard (admin.html)
A separate, site-wide (not per-team) page gated to site admins:
- Teams -- create/archive teams
- Site Admins -- grant/revoke site-admin access by Discord ID
- Guild Officers -- grant/revoke guild-wide officer access by Discord ID (view + player/attendance/bio edits on every team, without site-admin write access)
- BoE -- grant/revoke the BoE manager role by Discord ID (guild-wide; it gates every BoE money mutation), plus the guild-wide payout floor and pivot
- Feature Flags -- the same per-team flags as officer.html's Admin tab, in one cross-team table
- Audit Log -- cross-team, searchable
- Maintenance Mode -- site-wide banner + data-load gate
Auth, sessions, and access control
- Discord OAuth via Supabase Auth is the only login method, for raiders, officers, and admins alike -- one button, one flow.
- Character claim links a raider's Discord identity to a
players row (team_members + claim_character()); a person can claim characters on multiple teams.
- Officer access is a
team_members.role value (officer/team_leader), not a separate credential -- granted/revoked from the Roster tab's Discord Claims sub-tab or the Admin tab.
- Site-admin access is a
site_admin row in the guild_grants table, granted by Discord ID from admin.html.
- Every write path is enforced by Postgres Row Level Security, not client-side checks -- see
docs/RLS.md for the full policy/function matrix.
Architecture
- Supabase Postgres is the single source of truth -- schema and RLS policies live in
supabase/migrations/, applied in order by the Deploy workflow when a PR merges, ahead of the site that release ships.
index.html, officer.html, admin.html, guild.html, and boe.html are plain static pages (no build step, no bundler) that call Supabase directly from the browser via supabase-js, using a public anon key restricted by RLS.- Feature flags (
team_settings.config.features) let a team hide tabs/sub-tabs it doesn't use, editable per-team from the Admin tab or site-wide from admin.html.
- Every page is hosted on GitHub Pages at the repo root, published by
.github/workflows/deploy.yml after that release's migrations and Edge Functions are on production; the TEAMS object in js/common.js maps each team slug to its Supabase team ID, switched via ?team=. guild.html and boe.html are the exceptions: both are guild-wide and carry no team; the guild page links down into the team pages, and the BoE page shows every team's finds and asks which team a new find is for. boe.html reads a ?team= when one is given, purely to preselect that dropdown.
- Google Sheets/Apps Script was the original backend but has been fully retired (the migration's last phase closed 2026-07-21); the old
.gs source was removed from the repo once it was no longer needed even as historical record.
For the full file-by-file breakdown, local dev setup (Docker + Supabase CLI), migration workflow, and PR requirements, see CONTRIBUTING.md -- that's the maintained source of truth for project structure so it doesn't drift out of sync with this file the way it previously did.
Database
dbdoc/ -- generated schema docs (tables, columns, triggers, functions, ER diagrams), regenerated with npm run db:docs. Never hand-edit.docs/database-schema-reference.md -- a narrative companion to dbdoc/.docs/RLS.md -- hand-maintained policy/function reference (tbls can't generate this).docs/database-decisions.md -- a running log of settled schema decisions and the reasoning behind them; each entry names the migration that shipped it, and CI checks that the file exists.docs/season-inventory.md -- every season column and team_settings.config key: who writes it, who reads it, the format it holds, and whether it means the guild's tier or a team's own cycle. The input to the Season milestone's schema steps.docs/backup-restore.md -- what's backed up, what's regenerable without a backup, and the restore runbook.docs/app-preview.md -- the new app's private preview: what a tester needs, adding and removing testers, and how it is deployed and locked.
Local development
See docs/supabase-local-dev-setup.md for setting up the local Supabase stack (Docker + CLI) from scratch.
To see a PR's migration running under the site before it merges, section 10 of
that document is four commands from migration:new to localhost:3000 signed
in as a seeded persona.
npm run lint # eslint over js/, scripts/, tests/
npm run format:check # prettier check over js/, scripts/, tests/ and the Edge Functions
npm run typecheck # tsc --noEmit (js/common.js is @ts-check'd)
deno check supabase/functions/*/index.ts # type-check the Edge Functions (deno via scoop)
deno lint # lint them; scope and rules live in deno.jsonc
deno task test # their tests under tests/edge/, no permissions granted
npm run test:frontend # vitest -- frontend logic, no browser needed
npm run test:rls # vitest -- RLS policy behavior against a local reset
npm --prefix bot test # vitest -- the Discord bot, which keeps its own deps and gates
npm run db:docs # regenerate dbdoc/ after a migration change
npm run db:rls # regenerate docs/rls_policies.csv
npm run migration:new -- <slug> # new migration, stamped from the Eastern clock
npm run serve # serve the site at localhost:3000 against the local stack
npm run dev:login -- phoenix-officer # print a sign-in link for a persona; no name lists them
npm run dev:sink # catch what the Edge Functions would post to Discord
npm run db:snapshot # load the nightly production dump into the local stack
See CONTRIBUTING.md for the full PR checklist (what a migration change additionally requires) and versioning/changelog rules.
Roadmap
Planned work lives on the milestones, and the build order across them is on the open tracking issue.
