> For the complete documentation index, see [llms.txt](https://www.ftcwiki.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ftcwiki.org/site-introduction/welcome-to-ftc-wiki.md).
# Welcome to FTC WIKI
We hope you enjoy your stay....
**This Wiki’s Purpose**
This initiative is designed for current or aspiring *FIRST* Tech Challenge mechanical members. This guide will outline the beginner and intermediate aspects of *FIRST* Tech Challenge mechanics. This encyclopedia has been designed for individuals with some experience in building and assembling things, but who are stuck between skill levels where resources are either too basic or just a little above their heads. Hopefully, by the end of this guide, you will have a deeper understanding of the mechanical aspects of robotics.
**About us**
We are FTC Alumni from Scotch Plains, New Jersey, veteran members of Team 17670 for 4 years, and Team Captains. We’ve both been building for 4 years and are active members in the online FTC community. We have experience with multiple build systems, including Tetrix and Gobilda, and have created many iterations of Swerve drive.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://www.ftcwiki.org/site-introduction/welcome-to-ftc-wiki.md?ask=&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 `build a script that syncs our docs to a CMS` 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.