fix(join): describe the process we actually have, not one we don't - #207
Merged
Conversation
The four-step timeline on /join promised applicants a shortlist by domain leads, then "a brief conversation or short task", then onboarding. None of that has been decided — everything after submission is being handled from the response sheet for now. Step 03 was the real problem: it tells people to expect a conversation or a task. If that round never happens, applicants are left waiting on something we implied. Cutting to three steps says less but stays true, and "we'll email you about what comes next" covers whatever the process turns out to be. Also drops the "transparent, friendly, and learning-focused" subtitle, which described a selection process rather than saying anything, and narrows the grid to three columns to match.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
barunaniket
requested review from
hagemaruwu,
shivanshpap and
vaibhavtulsian
as code owners
September 9, 2026 13:45
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
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.
Follow-up to #204, flagged in that review. Copy only — no logic changes.
The problem
The "What happens next" section described a four-step process:
None of that has actually been decided. Everything after submission is being handled from the response sheet.
Step 03 is the one that matters. It tells applicants to expect a conversation or a task. If that round never happens, people are left waiting on something we implied and never said otherwise about. That's a bad first impression for a club whose pitch is that it's welcoming to first-years.
Steps 02 and 04 are softer versions of the same issue — "domain leads" and "platform access set up" both describe machinery that may not exist yet.
The change
Three steps, all of them true today:
"We'll email you about what comes next" deliberately covers whatever the process turns out to be — an interview, a task, or a straight yes. Nothing to rewrite later if the plan firms up differently.
Also drops the section subtitle ("Our selection process is designed to be transparent, friendly, and learning-focused"), which described a process rather than saying anything, and narrows the grid from four columns to three to match.
There's a comment above the array explaining why it's three steps, so the next person doesn't helpfully "complete" it back to four.
Verified
npx tsc --noEmitclean ·npm run lint0 errors (4 pre-existing warnings, untouched files) ·npm run test90/90 ·npm run buildsucceeds.