> 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/readme.md).

# Overview

How RAID Robotics (FRC Team 4469) presents itself, and why consistency matters.

## Branding

Our branding is the overarching image that represents the people and ideas of our team. A strong, distinctive brand lets us stand out among other FRC teams. The brand is more than our team name and logo — it is how we represent ourselves in everything we do, and it is the face people remember and attribute our successes to.

## Brand management

To position ourselves as a recognizable FRC team, we follow every part of these guidelines. Consistency across all communication, and in how we present ourselves, lets the brand grow and be instantly identified in the community.

## This guide

These pages cover every part of the RAID brand and should be followed at all times. They are based on the **2022 Brand Standards**.

{% hint style="success" %}
**Need a logo or template?** Every approved file is in the [Asset Library](https://docs.raidrobotics.org/brand/asset-library/asset-library.md), ready to download.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Naming</strong></td><td>Official name, nickname, approved aliases and hashtags.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/naming.md">Naming</a></td></tr><tr><td><strong>Colors</strong></td><td>AI Yellow, Raider Red and the accent palette.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/colors.md">Colors</a></td></tr><tr><td><strong>Logos</strong></td><td>Logo parts, clear space, minimum sizes and colorways.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/logos.md">Logos</a></td></tr><tr><td><strong>Icons &#x26; Lockups</strong></td><td>The number and name icons, and text lockups.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/icons-and-lockups.md">Icons &amp; Lockups</a></td></tr><tr><td><strong>Graphic Elements</strong></td><td>Lines and the gear pattern.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/graphic-elements.md">Graphic Elements</a></td></tr><tr><td><strong>Using Brand Assets</strong></td><td>Which file to use, and what you may not change.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/using-brand-assets.md">Using Brand Assets</a></td></tr><tr><td><strong>Typography</strong></td><td>IBM Plex, backup fonts and the text style guide.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/typography.md">Typography</a></td></tr><tr><td><strong>Templates</strong></td><td>Approved templates for team documents.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/templates.md">Templates</a></td></tr><tr><td><strong>Apparel</strong></td><td>When to wear team shirts and headwear.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/apparel.md">Apparel</a></td></tr><tr><td><strong>Sub-brands</strong></td><td>App logos, anniversary and specialty marks.</td><td><a href="https://docs.raidrobotics.org/brand/brand-standards/sub-brands.md">Sub-brands</a></td></tr></tbody></table>

{% hint style="info" %}
Questions about the brand, or need an asset or template that doesn't exist yet? Contact the **business team**.
{% 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/readme.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.
