Skip to content

fix(join): describe the process we actually have, not one we don't - #207

Merged
barunaniket merged 1 commit into
mainfrom
fix/join-timeline-copy
Sep 9, 2026
Merged

fix(join): describe the process we actually have, not one we don't#207
barunaniket merged 1 commit into
mainfrom
fix/join-timeline-copy

Conversation

@barunaniket

Copy link
Copy Markdown
Collaborator

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:

01 Application Submit your details and domain preference
02 Review & Shortlist Reviewed by the respective domain leads
03 Interaction / Task A brief conversation or short task
04 Onboarding Meet your peers, get platform access

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:

01 Apply Fill in the form above, pick one domain
02 We read it Every response is read — no filter to get past first
03 We get in touch If shortlisted, we'll email you about what comes next

"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 --noEmit clean · npm run lint 0 errors (4 pre-existing warnings, untouched files) · npm run test 90/90 · npm run build succeeds.

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.
@vercel

vercel Bot commented Sep 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
code-chef-pesuecc-chapter Ready Ready Preview Sep 9, 2026 1:46pm UTC

@barunaniket
barunaniket merged commit f95edf5 into main Sep 9, 2026
3 checks passed
@barunaniket
barunaniket deleted the fix/join-timeline-copy branch September 9, 2026 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant