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

# Media kit

Logos, product screenshots and approved descriptions of Lid, ready to use as they are.

Lid. The digital business suite.

Everything you need to write about Lid or feature us: descriptions you can paste, key facts, logos, colors, fonts, product screenshots and banners for events. Use them as they are.

### Download

Everything in one file: logos, colors, screenshots, banners and a README with the descriptions.

{% file src="/files/BxSUpEYXqqAAMjOhbFGQ" %}

The same files are in a Google Drive folder: [Lid Media Kit on Google Drive](https://drive.google.com/drive/folders/1Ip833dHBiZo4lo--65BK86b--XNaGZMN).

### What is inside

| Page                | What you will find                                     |
| ------------------- | ------------------------------------------------------ |
| About Lid           | Descriptions in English and Spanish, and the key facts |
| Logo and brand      | Logos, colors, fonts and how to use them               |
| Product screenshots | Real screens from lid.pro                              |
| Events and partners | A listing blurb and banners                            |

### Press contact

Alberto Fernández, co-founder and CEO. Email <hello@lid.pro>. We reply in English and Spanish.


---

# 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.lid.pro/company/media-kit.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.