> For the complete documentation index, see [llms.txt](https://docs.tvvin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tvvin.com/press-kit.md).

# Press Kit

**TVVIN Logo**

Our logo symbolises our core vision and values, representing the essence of our brand identity. Learn how and where to appropriately apply our emblem, ensuring the correct sizing and clear space around it, while also understanding what not to do with it. 

For more information, visit: [TVVIN Logo](/press-kit/tvvin-logo.md)

**Colours** 

The vibrant shades we employ reflect our distinct mission and personality as a brand. Discover the guidelines for using our primary and secondary colour palettes, defining the visual language that embodies our brand's essence. 

For further details, visit: [Colours ](/press-kit/colours.md)

**Typography Guidelines** 

The TVVIN typography guidelines encompass font styles and typographic treatments that harmoniously complement our brand identity. This detailed guide outlines our preferred typefaces, their applications, and the recommended sources for acquisition. 

For additional insights, visit: [Typography](/press-kit/typography.md)

The TVVIN team greatly appreciates your collaboration in maintaining our brand's compelling and cohesive identity.


---

# 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.tvvin.com/press-kit.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.