> For the complete documentation index, see [llms.txt](https://polee.me/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polee.me/help/en/blog/how-to-design-an-effective-cover-image.md).
# How to Design an Effective Cover Image
#### Your cover isn’t just a background — it’s the emotional tone of your profile. It complements your avatar and immediately sets the context for what you do.
Choose colors and visual elements that harmonize with your avatar and upcoming content. Think of each color like a musical note: together, they create a sense of unity and completion.
For a consistent and professional profile design, pick background colors and textures that align with your avatar and upcoming posts. A well-balanced color palette helps establish your brand identity and creates a unified visual impression.
The key is to avoid clutter and maintain a strong visual focus. Let the attention stay on you and your work not on distracting elements.
**Tip:** Avoid using small text on your cover. It may look unreadable on mobile devices. If you must include words, keep it short and bold a slogan or a few well-chosen emojis can do the trick.
**Polee cover recommendations:**
* Use a 2:1 format.
* Keep important elements away from the avatar zone — place them in the bottom left corner.
**Design your cover on** [**Polee.me**](https://polee.me) **as if it were a warm welcome. Make it clear, inviting, and worth coming back to. Good luck and happy creating! ✨**
---
# 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://polee.me/help/en/blog/how-to-design-an-effective-cover-image.md?ask=&goal=
```
`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.