> 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/getting-started/new-member-main-page.md).

# New Member Guide

This page is just a simple overview of everything, for more in-depth insight refer to the link of the said info.

## Introduction

This page will guide new members over how the robotics year will look like, over the tools we will use(including programming language, VS Code, over all things wpilib and rev), and all hands-on robot work you might do over this and upcoming years.

## Year Overview

#### Fall

We have an on-season(from September to June) and off-season(Summer break) period. On-season period is divided into two part 'pre kick off' and 'kick off season'.

During the fall, we work on learning how to do everything FRC. This takes place via working on small and large projects that all members can contribute to.

#### Build Season

Controls Systems students are expected to develop code and assist the build team in designing control systems and wiring layouts

#### Competition

Students support debugging and feature improvements during and between competitions

## Next steps

Work through the [learning path](https://docs.raidrobotics.org/programming/readme.md#learning-path), starting with [Tools](https://docs.raidrobotics.org/programming/getting-started/tools.md).


---

# 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/getting-started/new-member-main-page.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.
