> For the complete documentation index, see [llms.txt](https://wiki.purduesigbots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.purduesigbots.com/judging/resources/community.md).

# Community Resources

Throughout the VRC community, several teams and independent parties have published their own resources to help aid teams in their journey through the Judging Process. This is a brief compilation of our favorite community resources! For any questions and concerns, please reach out to us through the link on our home page.

{% hint style="danger" %}
These resources do not exist to be copied! Use the resources to help shape your own original work. Experienced judges will see copies enough to notice!
{% endhint %}

{% hint style="warning" %}
The older a Notebook or Resource becomes, the more dated it may be in accordance to the Rubric, as well as quality compared to more current sources. Regardless of whether or not it is on this page, take older resources with a grain of salt.
{% endhint %}

<table><thead><tr><th width="129">Author</th><th width="180">Resource</th><th>Strength</th><th>Link</th></tr></thead><tbody><tr><td>RECF</td><td>Guide to Judging</td><td>Read this above all else!</td><td><a href="https://v5rc-kb.recf.org/hc/en-us/categories/9625677270807-Judging?sc=guides">Link</a></td></tr><tr><td>BLRS2</td><td>Over Under Season Notebook</td><td>Overall format and content included</td><td><a href="https://drive.google.com/file/d/1GdnGnEY0ImQ-5ri8AZMvrpdxeO9koe6f/view">Link</a><br><a href="https://www.youtube.com/watch?v=k_QbcJR2J5o">Explanation Video</a></td></tr><tr><td>2654E</td><td>High Stakes Season Notebook</td><td>Explanation of technical and high-level content</td><td><a href="https://2654e.netlify.app/nb.pdf">Link</a><br><a href="https://youtu.be/33GlOvKLITM?si=Ud7oE--6pD5bCtoG">Explanation Video</a></td></tr><tr><td>515R</td><td>Spin Up Season Notebook</td><td>Essentials of a successful notebook</td><td><a href="https://drive.google.com/file/d/1HaW4U9oFkCO0W1oqMPX5Eugy24MAw_wm/view">Link</a><br><a href="https://www.youtube.com/watch?v=KNKPfB-uvCQ">Explanation Video</a></td></tr><tr><td>9MotorGang</td><td>Notebook Explanation/Tutorial</td><td>Introduction video for notebook basics</td><td><a href="https://youtu.be/j7KIrDFaDvc?si=Y2lKLvI6w_8n_qet">Link</a></td></tr></tbody></table>


---

# 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://wiki.purduesigbots.com/judging/resources/community.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.