Create starter guide for new programmers

Open
#43 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
java

Research direction

Start by reviewing the existing WPILib Zero to Robot guide and the 2025-Robot-Code and coppercore repositories. Document cloning the 401 repositories, expected directory structures, simulator/model setup, additional assets, and required configuration without duplicating WPILib material. Done means a student can prepare a new laptop, run the most advanced 2025 robot simulation, and see changes to both repositories reflected in it.

Written by the indexing model from the issue text.

Description

As discussed with @aidnem and @avidraccoon today, we need a starter guide for new programmers.

This guide should not repeat/duplicate from WPILib's Zero to Robot. We also assume basic familiarity with Java + Maven.

Instead, it should focus on:

  • how to clone 401 repositories and any expected directory structures
  • simulator/model setup, including additional assets
  • any necessary configurations.

The goal is that a student following the guide would start with a new laptop and end up with an environment in which they can run the most advanced simulation of the 2025 robot code. (Perhaps autonomous?)

As a second step, the guide should explain how to make changes to both 2025-Robot-Code and coppercore and then how to see those changes reflected in the simulation.

Outside of the scope of this guide would be:

  • general explanations of robotics concepts
  • information that can be found in wpilib (though links would certainly be welcome).
Dominant language
No language data
Stars
3
Forks
0
Avg merge
1m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from team401/Docs

All issues in team401/Docs

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.