> 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/icons-and-lockups.md).

# Icons & Lockups

Auxiliary marks — the standalone icons and the text lockups.

## Icon sets

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><strong>Primary icon</strong></td><td>Name Icon · "RAiD 4469"</td><td><a href="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-d31a9339cd68d8b469c05d395c339c158161d368%2FRAID-Name-Icon-RGB.svg?alt=media">RAID-Name-Icon-RGB.svg</a></td></tr><tr><td><strong>Secondary icon</strong></td><td>Number Icon · "4469"</td><td><a href="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-b2bd7c695f9d27e88a934bb67abbe05b5f2972f1%2FRAID-Number-Icon-RGB.svg?alt=media">RAID-Number-Icon-RGB.svg</a></td></tr></tbody></table>

### Primary icon (Name Icon)

Drawn from the shape of the logo's icon, the primary icon stands alone to identify the team. In **informal** documents and communication it can be used in place of the logo.

### Secondary icon (Number Icon)

The icon from the logo, adopted as a standalone mark for extra branding where needed. It should **never** be used on its own except for:

* Team buttons
* Competition fliers
* Team apparel

### Icon usage

|                            |                                                                                      |
| -------------------------- | ------------------------------------------------------------------------------------ |
| **Minimum size (digital)** | 75 px                                                                                |
| **Minimum size (print)**   | 0.625 in                                                                             |
| **Clear space**            | The distance from the edge of the gear to the top of the first circuit, on all sides |

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-71df5888b6b2bc0dd0340a9c7e71fe151a37ac84%2Ficon-clearance-sizing.png?alt=media" alt="Icon clear space diagram and minimum size of 0.625 inches or 75 pixels" width="560"><figcaption><p>Icon clearance and minimum size</p></figcaption></figure>

### Colorways

Both icons have wireframe and full-color versions in several colorways: **Primary, Inverse, Outline, Black** and **White**. Keep maximum contrast with the background, and use full-color versions before wireframe single-color ones.

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-b44fe0f083c9a204516434e9ba6a90adcea04c0c%2Ficon-colorways.png?alt=media" alt="Primary and secondary icons in primary, inverse, outline, black and white colorways"><figcaption><p>Icon colorways</p></figcaption></figure>

## Text lockups

Use the vertical or horizontal text lockup when there isn't room for the logo or the icons — for example, in a document footer.

| Lockup            | Min. size (digital) | Min. size (print) |
| ----------------- | ------------------- | ----------------- |
| Vertical lockup   | 60 px               | 0.5 in            |
| Horizontal lockup | 90 px               | 0.75 in           |

* **Clear space:** at least the height of the text on all sides. The dividing line may extend into the clear space.
* **Color:** always a single color — black or white — with clear contrast against the background.

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-9db8623fb2521a4ec1639578f4554aedbd6bd129%2Flockups.png?alt=media" alt="Horizontal and vertical lockups with clear space and minimum sizes"><figcaption><p>Horizontal and vertical lockups</p></figcaption></figure>

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><strong>Horizontal lockup</strong></td><td>Black · SVG</td><td><a href="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-dc298860174d73fb5fd897802ef9a0345ec46d41%2FRAID-Horizontal-Lockup-RGB-Black.svg?alt=media">RAID-Horizontal-Lockup-RGB-Black.svg</a></td></tr><tr><td><strong>Vertical lockup</strong></td><td>Black · SVG</td><td><a href="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-2ac474a4eb359832d7fe72e435674ca89cbd2ac0%2FRAID-Vertical-Lockup-RGB-Black.svg?alt=media">RAID-Vertical-Lockup-RGB-Black.svg</a></td></tr></tbody></table>

White versions of every icon and lockup are in the logo package — see [Using Brand Assets](https://docs.raidrobotics.org/brand/brand-standards/using-brand-assets.md).


---

# 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/icons-and-lockups.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.
