fix(site): Add inline guidance to member signup - #83
Merged
Merged
Conversation
Show short reasons for the information the join form requests, including how often email arrives and how interests guide suggestions. Put validation errors beside the affected fields as well as in the summary when someone continues with missing or malformed basic details. Co-authored-by: Codex <noreply@openai.com>
WillieCubed
had a problem deploying
to
worker-preview
October 1, 2026 17:42 — with 
GitHub Actions
Error
GitHub Actions
Error
Keep Astro's transitive serialization dependency on the patched 5.9 release so the production dependency audit remains clear. 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 member join form now explains why LVBT asks for each piece of personal information, directly beside the fields. Basic-info errors appear inline when someone presses Continue.
Overview of Changes
Short hints explain where the welcome email and weekly updates go, why LVBT asks for a first and optional last name, and how interest choices guide suggestions and transportation answers help LVBT understand how members get around. Existing phone and Discord explanations remain in place.
When someone presses Continue with missing or malformed basic details, the form now shows the relevant error beside each field and links to those fields from the summary. Error text is associated with the field for assistive technology. The server-rendered error path still supports visitors without JavaScript.
CI identified a newly reported high-severity issue in Astro’s transitive
devaluedependency. The PR pins its patched 5.9.4 release;pnpm audit --prod --audit-level=highnow reports no known vulnerabilities.pnpm checkpassed. In a 390px browser, the hints appeared on both stages. Missing email, first name, and consent appeared inline; a malformed phone number appeared inline; correcting the fields cleared their errors and allowed the optional stage.Follow-ups
None.