> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/core-product-structure/product-catalog-offering/content-and-branding.md).

# Content and branding

BAU rules for banners and content updates, plus asset specifications.

### Overview

Brands can update **homepage banners** and selected **content elements** across **Web**, **Mobile Web**, and **App**.

This section lists the **BAU specs** and what to provide during **requests**.

{% hint style="info" %}
Anything outside these parameters is treated as custom work.
{% endhint %}

### Banners and content updates

| Item                                    | Specification                               | What the brand provides                                     |
| --------------------------------------- | ------------------------------------------- | ----------------------------------------------------------- |
| Banner images                           | Desktop: 1440×500px                         | NA                                                          |
| iPad: 768×500px                         | NA                                          | NA                                                          |
| Mobile Web: 375×210px                   | NA                                          | NA                                                          |
| App: 343×150px (transparent background) | Separate image assets for each device type. | NA                                                          |
| Formats                                 | PNG or JPEG                                 | Keep each image ≤ 500 KB.                                   |
| Headline                                | Max 76 characters (including spaces)        | Headline text and hex color code.                           |
| Sub-heading (optional)                  | Max 60 characters                           | Text + display type (sentence vs bullets) + hex color code. |
| Color codes                             | Hex                                         | Provide hex codes for each text element.                    |

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at <account-desk@reachplatform.com> for help and support.
{% 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.reachplatform.com/core-product-structure/product-catalog-offering/content-and-branding.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.