Add a walkthrough and shortcuts for non-technical contributors - #3
Merged
Conversation
Everything written so far assumed the reader knew what a branch was. Someone who just wants Jane Doe on the mentors page had nowhere to start. GUIDE.md starts from having no accounts at all: sign up for GitHub, get added to the org, get Claude access, then a worked example of adding a mentor from first message to published. It names the things people will actually hit — the missing Merge button is deliberate rather than broken, preview pages carry a badge so they are not mistaken for the live site, changes can be iterated on before anyone sees them — and ends with a glossary so the GitHub vocabulary is decodable rather than a wall. Four skills in .claude/skills/ turn the common jobs into /add-mentor, /add-sponsor, /update-events and /new-season. They prompt for exactly what each task needs, and encode the mistakes already made once: event codes that must match their venue after North Charleston was linked to the Pembroke event, sponsor logo dimensions that must be read off the file rather than guessed, season results that must come from The Blue Alliance rather than last year's block. Claude can also load them from plain English, so nobody has to memorise a command. For anyone who will not use Claude, an issue form collects the same information in a plain web form for a maintainer to action, with blank issues turned off so the form is the path of least resistance. Each skill ends by pointing back at "Handing work back" in CLAUDE.md, so a change made through a shortcut still arrives with screenshots and a preview.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
lynk-website | f2a68bc | Commit Preview URL Branch Preview URL |
Aug 16 2026, 04:38 AM |
Team mentors hand out the Claude account, so the guide no longer sends people off to work out plans for themselves. Setup gains a step for connecting GitHub and granting access to LynkRobotics/website, which is what lets Claude push a branch and open a pull request, and says plainly that approving it does not let Claude publish. Nothing on the non-technical path now mentions a terminal: the local npm instructions move out of README's everyday workflow into a section marked for developers, and CONTRIBUTING labels its manual route the same way. GitHub access questions go to [email protected]. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01JwRVGEYx7WxaNm8yvxSrUZ
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
2 participants
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.
What changes
Everything written so far assumed the reader knew what a branch was. Someone
who just wants Jane Doe on the mentors page had nowhere to start. Three things
fix that.
GUIDE.md— a walkthrough from nothing to a published change. Sign up forGitHub, get added to the org, get Claude access, then a worked example of adding
a mentor from first message to live. It names the things people actually trip
on: the missing Merge button is deliberate rather than broken, preview pages
carry a badge so they are not mistaken for the live site, and a change can be
revised as many times as you like before anyone sees it. A glossary at the end
makes the GitHub vocabulary decodable.
Four shortcuts in
.claude/skills/—/add-mentor,/add-sponsor,/update-events,/new-season. They prompt for exactly what each job needs.Claude can also load them from plain English, so nobody has to memorise a
command.
They also encode mistakes this site has already made once:
update-eventsadd-sponsornew-seasonadd-mentorAn issue form for anyone who will not use Claude at all — same information,
plain web form, a maintainer actions it. Blank issues are off so the form is the
path of least resistance.
Each skill ends by pointing back at "Handing work back" in
CLAUDE.md, so achange made through a shortcut still arrives with screenshots and a preview.
Pages affected
None — documentation and tooling only. The built site is byte-for-byte
identical, so there are no screenshots.
How to review
GUIDE.mdas if you had never seen GitHub — does anything assumeknowledge it should not?
about Claude access
/add-mentorin a Claude session on this branchOne thing to confirm
GUIDE.mdtells people to ask a maintainer whether the team has a Claude planthey should be added to, since Claude Code needs a paid plan. If there is a
specific arrangement — a team plan, or a named person who handles it — tell me
and I will put the real instruction in instead.
Generated by Claude Code