The official site for hackPHS 2026
From the project folder run
python wsgi.pyThen open http://localhost:3000
Press Ctrl+C in the same terminal to stop the server
The homepage links to team.html. Team names and assignments are stored in
scripts/team-data.js, using the organizer-approved October 13 roster. The two
directors share a row, and section directors appear before each section's organizer
list. Finance has two section directors. The page also thanks the volunteers. Keep the
team.html no-JavaScript roster in sync when changing the structured roster.
The completed Canva recap has a web-ready copy in assets/videos/, with its
original video preserved separately. Visitors get a dismissible welcome once per
tab session when opening the homepage; Watch the 2026 recap always reopens it.
/#recap opens it directly, while schedule/map anchor visits are not interrupted.
No audio/video autoplays. Closing pauses playback and restores keyboard focus.
The local Python server streams byte ranges so video playback and seeking work.
Run node --test tests/recap-team.test.mjs with Playwright available to check the
welcome, playback, seeking, dismissal, team hierarchy, links and phone layouts.
index.htmlcontains the page content and accessible markupstyles/contains focused stylesheets for the layout and each visual areascripts/contains the page behavior split by responsibilityassets/contains branding sponsor images and documentswsgi.pyruns the small local development server
Questions about the event can be sent to team@hackphs.tech
Registration and the waitlist are closed. The homepage and FAQ display the closed
status, including when JavaScript is disabled. scripts/registration.js shows the
registration status and waiver reminder after the hero scrolls out of view.
Registered attendees must print, complete, and bring the participant waiver and their ID to check-in. Participants under 18 also need a parent or legal guardian signature. The PDF is an unchanged copy of the organizer's waiver.
The homepage schedule and event details follow the logistics schedule. Elad Hazan's talk is Saturday, 11:30 AM–12:30 PM, per the organizer's correction.
Open /leaderboard.html, also linked in the main navigation. Update scores in
the existing Google Sheet as usual. The site reads only the Sorted Teams tab
(gid 857309), columns A and B, with the headers Teams and Score.
Keep that tab in the desired ranking order. Equal adjacent scores share a rank;
the site does not recalculate totals or sort the raw event scores.
The sheet must remain viewable by anyone with the link. Only share team names
and scores, not private attendee information. Sharing the whole workbook makes
its other tabs public too. For tab-only publishing, publish Sorted Teams as CSV
and replace standingsUrl in scripts/leaderboard-data.js with that published URL.
The page polls every 30 seconds while visible and refreshes when reopened or when Refresh is clicked. Google may cache results briefly. On connection failure, the last successful standings remain visible and are labeled as out of date. An empty sheet shows an awaiting-scores state, not example teams. A team with a blank score waits for a score; zero is a valid score. Formula errors are reported as unavailable updates instead of becoming fake scores.
Event dates remain October 10-11, 2026, as confirmed by the organizers. The linked event guide is maintained separately and still needs its dates corrected.
Workshop and competition responder links appear at 9:00 AM New York time on
Saturday, October 10, 2026 (2026-10-10T13:00:00Z, EDT / UTC−4). The shared
logic in scripts/event-signups.js updates both event dialogs and standalone
event pages, including pages left open at the release time. This is a display
schedule based on the visitor's device clock, not an access-control boundary.
The code must be deployed before release for this behavior to appear publicly.
Sign-ups close on the website at the event's end, noon New York time on
Sunday, October 11, 2026 (2026-10-11T16:00:00Z). The notice, event dialogs,
and standalone event pages show closed status and no responder links afterward.
Pages already open also update at the closing boundary.
Competition URLs remain archived in competitiveSignupUrls in scripts/events.js.
On October 13, the workshop form and all six competition/voting forms still
displayed questions and a Submit button. Their owners need to stop accepting
responses in Google Forms separately. No form settings or responses were changed.
The participant map PDF is an unchanged copy of the organizer's supplied file. Its PNG preview supports zoom, pan, pinch, keyboard controls and full screen; the original PDF remains available for opening or downloading. The map's printed event timeline has differences from the current website schedule, so the viewer directs participants to the schedule for current times and rooms.
Run node --test tests/event-updates.test.mjs with Playwright available to check
release timing, responder URLs, map controls, prize updates and mobile layouts.
The website and Python preview do not need Node or npm. If Node is already
available, run the data checks with node --test tests/data.test.mjs.
Browser checks use Playwright and Edge: with the Python preview running and
Playwright available to Node, run node --test tests/browser.test.mjs.
Those checks include the real public sheet connection, mocked score updates and
outages, closed registration and waitlist status, schedule rooms, and phone layouts.
Test teams are browser-only fixtures and are never written to the Google Sheet.
/judging uses exclusive tablesets of five projects, the existing rubric, and a final within-set ranking
worth 15/10/5/0/0 points. There is no calibration or finals round. Ties remain for organizers to resolve.
Names come from the source spreadsheet's Judges tab and project details from Expo, through server-side Apps Script.
The browser never receives the source spreadsheet ID, judge roster, or overall standings.
See judging/README.md for required backend deployment, private results setup, and Devpost CSV import.
The Apps Script backend must be redeployed alongside the frontend; mismatched versions refuse sign-in.