> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/programming/readme.md).

# Programming

How the controls subteam learns to program the robot. New members work through the learning path in order; everyone uses the [Robot Template](https://docs.raidrobotics.org/robot-template/) as the starting point for each season's code.

## Learning path

| Step | What                                                                                                                                         | Time                             |
| ---- | -------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |
| 1    | [New member guide](https://docs.raidrobotics.org/programming/getting-started/new-member-main-page.md): how the year works for controls       | 10 min                           |
| 2    | [Tools](https://docs.raidrobotics.org/programming/getting-started/tools.md): install WPILib and the tools we use                             | 1 meeting                        |
| 3    | [Java](https://docs.raidrobotics.org/programming/learning/java.md): the Codecademy course, first 5 modules required                          | about 17 hrs for the full course |
| 4    | [Command-based programming](https://docs.raidrobotics.org/programming/learning/command-based-programming-frc.md): how FRC code is structured | 1–2 meetings                     |
| 5    | [Robot Template](https://docs.raidrobotics.org/robot-template/getting-started/getting-started.md): our code, from install to simulator       | 1–2 meetings                     |
| 6    | [Control theory](https://docs.raidrobotics.org/programming/learning/control-theory.md): PID, feedforward and beyond                          | ongoing                          |

## Reference

* [Links](https://docs.raidrobotics.org/programming/reference/links.md): WPILib, vendor libraries and other docs we use
* [Robot Template glossary](https://docs.raidrobotics.org/robot-template/reference/glossary.md): terms used in our code
* [Electrical lessons](https://docs.raidrobotics.org/electrical/): what the hardware is and how it's wired
* [2025 season](https://docs.raidrobotics.org/programming/past-seasons/2025.md): last season's code and vendor dependencies


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.raidrobotics.org/programming/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
