> For the complete documentation index, see [llms.txt](https://iiwii-robotics.gitbook.io/engineering-notebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://iiwii-robotics.gitbook.io/engineering-notebook/vex-engineering-notebooks/overview.md). # Overview This guide is a supplemental resource to the information provided by the REC Foundation and VEX regarding the Engineering Notebook which can be found via the following links. [https://notebooking.vex.com](http://notebooking.vex.com/)\ [VIQRC Notebook Design Process](https://viqrc-kb.recf.org/hc/en-us/categories/9699851481367-Notebooks)\ [V5RC Notebook Design Process](https://v5rc-kb.recf.org/hc/en-us/categories/9625651590423-Notebooks) While the above information provides useful details around the overall Engineering Notebook practice, the information contained within this site is provided to give additional details that have been gleaned after competing for 7 years and winning Design at Worlds twice in 4 years. The intent of this site is not to duplicate the information provided above, but to give insight from one team/orgs viewpoint as to how to go about creating a useful notebook based on the Engineering Notebook Rubric Requirements. This is not an end all be all guide as we know each team has their unique approach to how they document their engineering design process and competition season journey. As we know that judges are not at liberty to provide notebook feedback, we wanted to try to give our best insight as to what might give a team an advantage in creating a notebook that covers as many rubric areas as possible. While the information contained within this site covers a number of areas, we realize that there are some items one may feel are missing or overlooked. While the information comes from winning design and excellence at a number of local, regional, signature, and world events we don’t claim this to be the best and know there are a number of great notebooks out there and some with better examples than ones being provided. If there are any team’s out there that would be open to sharing their process, notebooks, or ideas for inclusion in this site, we welcome the opportunity to include your work. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://iiwii-robotics.gitbook.io/engineering-notebook/vex-engineering-notebooks/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.