CSS Platform (V2): Technical README

The Chinese Students' Society's own event, ticket and membership platform: a mini Luma/Eventbrite built on free Google tools. Execs: you want HANDBOOK.md. Something broke: RUNBOOK.md.

Status: API 0.15.0 (the API_VERSION in api/Config.js; the Apps Script deployment label says the same). Events, registration, payments, door and the redesigned Exec Portal are live. Membership sign-up (member.ucalgarycss.ca/create), the Members tab's Pending list, Add member and Mark paid were added 2026-09-30. Roadmap and what is left: the vault note "CSS Platform - Roadmap". The old system (../CSS Ticketing System/) keeps running until this one is proven. Nothing here touches it.

---

1. How it fits together

 People                     Web pages (static files)              Back end                     Storage
 ─────────                  ───────────────────────              ─────────                    ─────────
 Public / attendees  ──►    public/        (event pages)   ──┐
 Execs               ──►    exec-portal/   (Exec Portal)   ──┼──► "CSS Platform API"   ──►   Google Sheets + Drive
                                                             │    (Google Apps Script
                                                             │     web app, api/)

• Pages are plain HTML/CSS/JS with no build step. Host them anywhere static (Vercel, GitHub Pages) or open them from disk.
• Every page talks to one back end: an Apps Script web app. The page sends POST with a JSON body { action, token, ...details } and gets JSON back: { ok: true, ... } or { ok: false, error: "CODE", message }.
• Storage:
  • Membership sheet (the existing one): only read so far, for member search and member-price checks.
  • "CSS Platform Data": a spreadsheet the back end created and owns. One tab per table (section 4).
  • "CSS Platform/Event images" Drive folder: uploaded event images, viewable by link.

2. Where everything lives

Thing	Where
Google account that owns everything	[email protected]
Apps Script project	"CSS Platform API", script ID 1xxpp4EJA-0uUhtwo9sOK9e1itomqN_29C6lwg3jzh35pabKJ-vOKnpMB. Editor: https://script.google.com/d/1xxpp4EJA-0uUhtwo9sOK9e1itomqN_29C6lwg3jzh35pabKJ-vOKnpMB/edit
Web app deployment ID	AKfycbxJ_a_cHyRXadK17ocIebhE2XDFcpEADCzSqOVXwdCgIQe1T-UPi-efzgla2mn7ML2d
Web app URL (API)	https://script.google.com/macros/s/<deployment ID>/exec. Opening it in a browser shows {"ok":true,...}
Platform data sheet	"CSS Platform Data" (may be renamed/moved; the system finds it by ID, stored in Script Property DATA_SHEET_ID)
Event images	Drive folder "CSS Platform/Event images" (ID in Script Property IMAGE_FOLDER_ID)
Local code	Chinese Student Society/CSS Ticketing System V2/ (OneDrive), a git repo
GitHub repo	https://github.com/cssuofcalgary/css-platform (can go private; Vercel is linked to it)
Public site (live)	https://events.ucalgarycss.ca/ (event page: /?e=<slug>, ticket: /ticket.html?t=<secret>)
Exec Portal (live)	https://exec.ucalgarycss.ca/ (door scanner: /scanner/). Layout: theme.css is the look (sidebar, cards, Overview, help-desk Door); the JS files are unchanged logic.
Hosting	Vercel for both sites (events and exec), built from the GitHub repo on every push to main, about a minute or two. The member pass site (member.ucalgarycss.ca) is a separate repo, cssuofcalgary/member-portal, also on Vercel. See "Hosting on Vercel" below. GitHub Pages is not used any more.

This is the beginning of the README. Read the rest at the original. Read the full README ↗