> For the complete documentation index, see [llms.txt](https://docs.monkeykingdom.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monkeykingdom.io/wiki/branding/brand-identity/previous-branding/typography.md).

# Typography

### Brand Font

**Press Start 2P** is a bitmap font based on the font design from 1980s Namco arcade games. It works best at sizes of 8px, 16px and other multiples of 8. We utilities the original font in Regular in our headers across all applications. When using Press Start 2P across our brand materials, the font can be used in both all caps and title case upon approval, and brand name should always be stylised in title case regardless of font.

<figure><img src="/files/1SLE6WRHTrG6QawvsQq9" alt=""><figcaption></figcaption></figure>

### Body Font

**Roboto** is the go to font for google ui and for android, and therefore gives a good tech background and feel just by visual association. Its grotesque construction means it retains the original evolutionary touch from the calligraphic-derived serifs to give our tech brand a more human element. The not too round curves that have a more elliptical shape and the medium aperture for the rounds work well to contrast the wide set but very angular header font.

<figure><img src="/files/yr2BBk7fQ7NllN7WInfS" alt=""><figcaption></figcaption></figure>

### Applying our typography

Whenever we use our brand name in written context as part of a sentence or a block of text, our brand name should always be stylised in title case ‘Monkey Kingdom’, regardless of font. This draws a connection between regular display of our brand name and our logo, and works to improve overall brand recognition.

<figure><img src="/files/Q8A1wjV3RgUoTCGU9zpv" alt=""><figcaption></figcaption></figure>


---

# 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://docs.monkeykingdom.io/wiki/branding/brand-identity/previous-branding/typography.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.