fix(site): Make join steps compact and clear - #79
Merged
Merged
Conversation
Put the join form's purpose ahead of its progress cue and keep both stages visible without crowding the first question on small screens. Label the optional stage for all the details it asks about. Co-authored-by: Codex <noreply@openai.com>
WillieCubed
had a problem deploying
to
worker-preview
October 1, 2026 03:04 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Read event links and titles after each page loads. The metadata is in server-rendered HTML, so waiting for unrelated network activity made the preview check exceed its time limit. Co-authored-by: Codex <noreply@openai.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
The membership join form shows a compact two-step progress cue and puts the page heading and first question higher on phones.
Overview of Changes
The progress cue now sits below the page introduction as a thin, single-line indicator. The second screen uses “Optional details” for its heading and step label, since it asks about interests, Discord, and getting around. The first-screen introduction is hidden on that screen so people can reach the optional questions sooner.
The form remains one usable page without JavaScript. With JavaScript, Back restores the first heading and preserves entered information. Local checks covered 320px, 390px, and 768px widths, both steps, no horizontal overflow, and the no-JavaScript flow.
The preview's browser suite exposed a recurring-event metadata test that timed out while waiting for network idle on 36 pages. Its links and metadata are available when each page loads, so the redundant waits were removed. The test passes against the Worker preview in about seven seconds.
pnpm checkpassed.Follow-ups
None.