> 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/brand/brand-standards/templates.md).

# Templates

Approved templates for team documents and print pieces.

The team has document templates built to follow these brand standards. **Always use them, and don't alter them.** If a new template is needed, the business team will create it.

## Document types that need a template

* Letters
* Business cards
* Standard operating procedures
* Brochures
* Fliers
* Social media posts
* Engineering documentation
* Presentations
* Buttons

## Available templates

Download them from the [Asset Library](https://docs.raidrobotics.org/brand/asset-library/templates.md).

| Template                  | Format                                   |
| ------------------------- | ---------------------------------------- |
| Letterhead                | Word (`.dotx`), Affinity (`.aftemplate`) |
| Team Document Template    | Word (`.dotx`)                           |
| Text Styles (Rebrand)     | Word (`.docx`)                           |
| Full Document Template V1 | Affinity (`.aftemplate`)                 |
| One Pager Template        | Affinity (`.aftemplate`, `.afpub`)       |
| Business Card             | Affinity (`.afpub`)                      |

## Examples

### Business card

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-55f86e56e5a53138887898b657092236bdceada1%2Fexample-business-card.png?alt=media" alt="Example RAID business card for Tommy Raider, Mascot" width="560"><figcaption><p>Business card</p></figcaption></figure>

### 2.25" button

| Image size | Cut size |
| ---------- | -------- |
| 2.063"     | 2.625"   |

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-a8cec948086e141a140b83f539582cb70910dcc9%2Fexample-button-spec.png?alt=media" alt="Button template showing a 2.063 inch image area and 2.625 inch cut line" width="320"><figcaption><p>Button image and cut size</p></figcaption></figure>

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-80dfc62661800532df05043f36b05181f7d6c9ca%2Fexample-button-photo.png?alt=media" alt="Finished yellow and red RAID 4469 buttons" width="520"><figcaption><p>Finished buttons</p></figcaption></figure>

{% hint style="info" %}
Don't see a template for what you're making? Contact the business team to have one created.
{% endhint %}


---

# 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/brand/brand-standards/templates.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.
