> For the complete documentation index, see [llms.txt](https://docs.ndi.video/brand/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/brand/brand-elements/typography.md).
# Typography
Typography plays a crucial role in embodying our brand values and communicating our vision effectively. We have carefully selected a font that captures the essence of our brand - universality, adaptability, and, above all, connection.
***
**Connected Sans** is our proprietary font. It features sink spots and distinctive curves within the characters, creating a unique and memorable visual identity. The uniqueness and character of our typography serve as an essential asset for our brand, setting us apart and reflecting our proprietary approach.
This bespoke typography reinforces our brand's identity and ensures a cohesive visual experience across all brand elements.
Organic curves accentuate a balanced geometric font.
Different weights inspire unlimited possibilities.
***
## Using Connected Sans
{% hint style="info" %}
In most contexts, you can only use our font as part of our logos (e.g., the NDI logo, the NDI HX logo, or the NDI Tools logo). If you require our font for special applications, don't hesitate to [**get in touch**](https://ndi.video/resources/get-in-touch/) with us.
{% 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.ndi.video/brand/brand-elements/typography.md?ask=&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.
