Right now we have an Installation section for general tooling (WSL for Windows, GitHub auth, etc.), but we don’t have a clear “I want to contribute” development path.
New contributors aren’t sure where to start depending on what they want to work on (docs vs website vs the actual car/robotics stack), and it makes it harder to distribute tasks.
Describe the solution you'd like
Create a new top-level docs page/section: Development for Contributors.
Inside it, add a simple dropdown/accordion (or clearly separated sections) for three contribution tracks:
- Docs
- Website
- Car / Robotics Stack
Each track should include:
- Prerequisites (only what’s specific to that track)
- Repo structure pointers (where the relevant code/docs live)
- “Run locally” steps (dev server / build / test)
- Common tasks (editing a page, adding a component, updating ROS package, etc.)
- “How to pick an issue” guidance and labeling expectations
Important: The existing Installation page should remain the source of truth for general tooling setup (WSL, GitHub auth, base dependencies). The new page should reference Installation instead of duplicating it.
Describe alternatives you've considered
- Keeping everything in Installation (but it gets long and mixes general setup with track-specific steps)
- Separate pages without a dropdown (fine too, but dropdown/accordion keeps it compact and beginner-friendly)
Additional context
Goal: make onboarding easier + allow us to distribute work by track (Docs / Website / Car) while keeping general setup centralized.
If possible, align the structure with issue labels so contributors can self-select tasks quickly.
Right now we have an Installation section for general tooling (WSL for Windows, GitHub auth, etc.), but we don’t have a clear “I want to contribute” development path.
New contributors aren’t sure where to start depending on what they want to work on (docs vs website vs the actual car/robotics stack), and it makes it harder to distribute tasks.
Describe the solution you'd like
Create a new top-level docs page/section: Development for Contributors.
Inside it, add a simple dropdown/accordion (or clearly separated sections) for three contribution tracks:
Each track should include:
Important: The existing Installation page should remain the source of truth for general tooling setup (WSL, GitHub auth, base dependencies). The new page should reference Installation instead of duplicating it.
Describe alternatives you've considered
Additional context
Goal: make onboarding easier + allow us to distribute work by track (Docs / Website / Car) while keeping general setup centralized.
If possible, align the structure with issue labels so contributors can self-select tasks quickly.