> 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/notion/purdue-sigbots-notion-template.md).

# Purdue SIGBots Notion Template

When beginning a new page in Notion, beginning with a template allows for a uniform format throughout the engineering notebook. The following templates are created as examples for teams to use as a reference. Teams are encouraged to read the Engineering Notebook Rubric before beginning to use these templates for additional information on key concepts to be included. 

{% hint style="warning" %}
These templates are for reference only. Teams should take inspiration from these templates, and create their own templates. They should NOT be copied. 
{% endhint %}

{% hint style="danger" %}
The following process does not allow the use of ***`emojis`***, only ASCII characters. These templates include emojis in call outs that should all be deleted before exporting.\
All emojis appear as a variation of "☒☒"
{% endhint %}

{% embed url="<https://sigbots.notion.site/Purdue-SIGBots-Wiki-Notebook-acbee863e319485885ebbb63d0ba1666?pvs=4>" %}
Notion Template Used throughout the following tutorials (created Dec. 2023)
{% endembed %}


---

# 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://wiki.purduesigbots.com/judging/notion/purdue-sigbots-notion-template.md?ask=<question>&goal=<endgoal>
```

`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.