Homepage redesign, About Us page, and Help / FAQ page

[Max-Harold]

Fills in the three public-facing pages. The homepage got a redesign, and /about and /faq — both of which shipped as "Page under development" stubs while being linked from the navbar on every page — are now real pages.

What's in it

Homepage redesign (829cfde) — a WebGL simplex-noise shader background (NoiseBackground) with a mouse-follow parallax, honouring prefers-reduced-motion and falling back to a CSS gradient where WebGL is unavailable. The AUTOGRADER wordmark sits above a dark frosted-glass hero panel. Removes the leftover /test page from all three places it was wired (Vite input, go:embed, Echo route).

Animated logo and classroom popup fix (6da65d5).

About page (68240cf) — a scrolling page of frosted panels: why the platform exists, what instructors and students each get, a four-step walkthrough of how grading works, the four supported languages, and who built it.

This commit also extracts the homepage's visual language into web/src/glass.css — the .glass panel with its opaque @supports fallback, .ghost-btn, and a .wordmark class holding the wordmark's glow filter — so it is shared rather than trapped in index.css.

Help / FAQ page (d438727) — 36 questions across four sections: getting started, using Autograder as a student, understanding your results, and instructors/TAs.

Adds FaqItem, a small accordion local to the page. The repo already has five expand/collapse implementations but none fit: ExpandPanel's API carries a grade percentage and its CSS assumes a light background, and all five put onClick on a <div> with no aria-expanded or keyboard handling. FaqItem uses a real <button> with aria-expanded/aria-controls and useId, and open state is lifted to the page so one "Expand all" control can drive every row — which is what keeps find-in-page usable on an accordion.

Notes for review

The FAQ content is drawn from the code, not assumed. The answers worth checking are the ones users are most likely to get wrong today:

• The password special-character set genuinely excludes -, =, [, ], \, | and backtick, so Passw0rd- is rejected.
• Output comparison ignores trailing whitespace and line endings but not spaces inside a line.
• A non-zero exit status fails a test even when the output is correct.
• If every test case on a question is hidden, the student sees no compile errors or stack traces at all — only FAILED (0/n points).

The page documents current limitations plainly rather than omitting them: there is no join code, no CSV grade export, no student-facing submission history, no shell test cases, and no email beyond invitations and password resets. Outright defects are deliberately left out of the copy (see below).

Four claims on the About page are corrected in the FAQ commit, so the two pages don't contradict each other: banner selection is an unimplemented placeholder popup, the assignment UI exposes only Draft and Visible (edit mode is unreachable), question points were dropped from the schema and are the sum of test-case points, and submission history is instructor-only.

Claims deliberately kept off both pages, because the code doesn't currently back them: nsjail sandboxing is built into the grader image but hard-disabled at grader.py:55, so the 256 MB memory cap isn't enforced. Copy claims only Docker isolation, non-root execution, per-test-case timeouts, and the output cap — all of which genuinely happen. Also no HTTPS, CSRF, or licensing claims.

Verification

• yarn build clean. Dropping the unused tailwindcss import from about.css and FAQ.css (it claimed the same --color-* namespace as colors.css) took those stylesheets from ~20.7 kB to 4.3 kB and 5.0 kB.
• The accordion was driven over the DevTools Protocol — 25 checks covering click open/close, Enter and Space on a focused question, unique aria-controls resolution across all 36 rows, the focus ring, expand-all in both directions, and no horizontal overflow at 480px.
• Screenshots at 1280px, 1100px and 480px; WebGL-disabled fallback confirmed; homepage and About re-checked for regressions after the glass.css extraction and the copy edits.

Follow-ups worth filing separately

Three real defects surfaced while researching the FAQ. None are touched here and none are documented on the page:

1. A re-sent invitation emails a new token but only persists it if no pending invite exists, so only the first invitation link ever works (service/auth.go:49-68).
2. An expired or used password-reset link shows the user the literal string login failed, because the handler returns a 500 with that message for every service-layer failure (handler/auth.go:382-385).
3. GetClassroomStudents sizes its result slice len(students)-1 assuming the caller is in the list, so it panics with a 500 for an admin who isn't a member of the classroom (service/classroom.go:219-228).

Also: web/tsconfig.app.tsbuildinfo is a TypeScript incremental-build artifact tracked in git, so it churns on every build. It probably belongs in .gitignore.

🤖 Generated with Claude Code