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

# Rich text

Add headings or text anywhere

Broadcast's rich text section is the simplest method for adding text or headings above or between sections. It allows you to add large or short messages with headings, subheadings, and text styles.

<figure><img src="https://2636770384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsD7BEEDU3B7WiEJlN0F7%2Fuploads%2FVgaE31rVYKQAx9uZk4Fa%2Frich-text.jpg?alt=media&amp;token=a65cfcdb-40df-46d4-8f0a-cb518ac73b4f" alt="An example of the rich text section displayed above an image"><figcaption></figcaption></figure>

### Section settings

<table><thead><tr><th width="206.951416015625">Settings</th><th width="154.0321044921875" align="center">Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Typography</strong></td><td align="center"></td><td></td></tr><tr><td>Text alignment</td><td align="center"><code>select</code></td><td>Aligns the text within the section: <code>Left</code>, or <code>Centered</code> . </td></tr><tr><td><strong>Layout</strong></td><td align="center"></td><td></td></tr><tr><td>Width</td><td align="center"><code>select</code></td><td>Defines the section width: <code>Full width padded</code>, <code>Normal</code>, or <code>Narrow</code>.</td></tr><tr><td><strong>Desktop</strong></td><td align="center"></td><td></td></tr><tr><td>Background image</td><td align="center"><code>image_picker</code></td><td>Adds a desktop background image. Recommended: 3200x1200px.</td></tr><tr><td><strong>Mobile</strong></td><td align="center"></td><td></td></tr><tr><td>Background image</td><td align="center"><code>image_picker</code></td><td>Adds a mobile background image. Recommended: 1200x1600px.</td></tr><tr><td><strong>Colors</strong></td><td align="center"></td><td></td></tr><tr><td>Color scheme</td><td align="center"><code>color_scheme</code></td><td>Selects the section’s color scheme.</td></tr><tr><td>Overlay type</td><td align="center"><code>select</code></td><td>Adds an overlay: <code>Disabled</code>, <code>Opacity</code>, or <code>Text underlay</code>.</td></tr><tr><td><strong>Padding</strong></td><td align="center"></td><td></td></tr><tr><td>Top</td><td align="center"><code>range</code></td><td>Top spacing in pixels.</td></tr><tr><td>Bottom</td><td align="center"><code>range</code></td><td>Bottom spacing in pixels.</td></tr></tbody></table>

### Video Overview

This video demonstrates the section settings and block options for the **Rich text** section:

{% embed url="<https://www.loom.com/share/a533eb6df1554a66980c8d182881596d?sid=dbe2d9f5-8515-47a2-9eb5-94e78f141065>" %}
**Video walkthrough of the rich text section**
{% endembed %}


---

# 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://broadcast.presidiocreative.com/sections/sections/text/rich-text.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.