> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/developer-guide/pt-br/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-collection/capsule-header-dimensions.md).
# Dimensões do cabeçalho da Cápsula
Veja as dimensões corretas do cabeçalho da Cápsula para encaixar na área do cabeçalho e manter a imagem com alta qualidade.
Cabeçalhos são usados em Cápsulas para indicar a qual coleção a Cápsula pertence. Ao criar uma nova coleção, você deve fazer upload do cabeçalho e selecionar a cor da cápsula.
As cápsulas possuem formato hexagonal e o cabeçalho está localizado na parte superior deste hexágono. Portanto, o tamanho da imagem do cabeçalho deve ser maior para preencher o formato hexagonal, mas o logotipo deve ser menor para ser totalmente exibido, conforme mostra a figura a seguir:
## Dimensões do cabeçalho
O arquivo de cabeçalho deve estar no formato `.jpg` ou `.png` e ter as seguintes dimensões:
* **Largura do cabeçalho:** 180px
* **Altura do cabeçalho:** 40px
* **Largura do logo:** 90px
* **Altura do logo:** 24px
Seu logo deve ser colocado centralizado na imagem. Dessa forma, você obtém um preenchimento de 8px na parte superior e inferior e um preenchimento de 45px em ambos os lados.
---
# 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.digibee.com/documentation/developer-guide/pt-br/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-collection/capsule-header-dimensions.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.
