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

# Typography

Team fonts, backups, and the text style guide for publications.

## Main fonts

Both IBM Plex faces are free on [Google Fonts](https://fonts.google.com/?query=IBM+Plex) and should be used whenever possible.

| Role           | Font               | Use                                                                                                                                |
| -------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Primary**    | IBM Plex Sans      | Titles and headings in printed documents, in various weights. Also the body text on the website and in most digital communication. |
| **Secondary**  | IBM Plex Serif     | Body text only, in printed documents and formal digital communication.                                                             |
| **Robot name** | SF Sports Night NS | Only for displaying the robot's name, in any form of communication. Free from DaFont. Don't substitute it.                         |

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-c050bc54b54ced999b1b8edebaa4ea7cc945c559%2Ffont-families-main.png?alt=media" alt="Main fonts: IBM Plex Sans, IBM Plex Serif, SF Sports Night NS" width="480"><figcaption><p>Main fonts</p></figcaption></figure>

## Backup fonts

If the main fonts can't be downloaded and used, use these defaults that come with most operating systems, following the same styles as the fonts they replace.

| Role      | Backup font        | Replaces       |
| --------- | ------------------ | -------------- |
| Primary   | Arial              | IBM Plex Sans  |
| Secondary | Century Schoolbook | IBM Plex Serif |

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-8ec63f43f7c8101ca37409bdce5310b3bc979cba%2Ffont-families-backup.png?alt=media" alt="Backup fonts: Arial and Century Schoolbook" width="480"><figcaption><p>Backup fonts</p></figcaption></figure>

Download links for every team font are in the [Asset Library](https://docs.raidrobotics.org/brand/asset-library/fonts.md).

## Text style guide

These type faces, sizes and styles give all team communication a polished, uniform feel. Follow this hierarchy in every document, and use best judgement while staying uniform across a whole document — for example, use Heading 1 for every new subsection. The [templates](https://docs.raidrobotics.org/brand/brand-standards/templates.md) already have these styles built in, so use them rather than recreating the styles.

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-99157caec76af0e2030701708ac5985ab1bce2bb%2Ftypography-style-guide.png?alt=media" alt="Typography style guide showing each text style rendered with its specification"><figcaption><p>Typography style guide</p></figcaption></figure>

| Style                | Specification                                      |
| -------------------- | -------------------------------------------------- |
| **Title**            | IBM Plex Sans Bold · 22 pt · All caps              |
| **Subtitle**         | IBM Plex Sans SemiBold Italic · 18 pt · All caps   |
| **Heading 1**        | IBM Plex Sans Bold · 14 pt · All caps · Raider Red |
| **Subheading 1**     | IBM Plex Sans Light Italic · 12 pt · Dark Gray     |
| **Heading 2**        | IBM Plex Sans Bold · 12 pt                         |
| **Subheading 2**     | IBM Plex Sans Light Italic · 11 pt · Dark Gray     |
| **Heading 3**        | IBM Plex Sans Medium Italic · 11 pt                |
| **Heading 4**        | IBM Plex Sans Medium Italic · 11 pt · Raider Red   |
| **Body**             | IBM Plex Serif · 11 pt                             |
| **Web/Digital body** | IBM Plex Sans · 10 pt                              |
| **Emphasis**         | Italic                                             |
| **Strong**           | Bold                                               |
| **Strong emphasis**  | Bold italic                                        |
| **Bold red**         | Bold · Raider Red                                  |
| **Accent line**      | Raider Red line on the left                        |
| **Bullet list**      | Em dash (–) bullets                                |
| **Caption**          | IBM Plex Sans Bold · 10 pt · All caps              |


---

# 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/typography.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.
