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

# Rich Text

A clean text band — headings, captions, paragraphs, and buttons on a colored background. Use it for brand statements, shipping notices, or intros between image-heavy sections.

## Section settings

| Setting              | What it does                                      | Default  |
| -------------------- | ------------------------------------------------- | -------- |
| Content position     | Where the text column sits: Left / Center / Right | Center   |
| Content alignment    | Text alignment inside the column                  | Center   |
| Color scheme         | Background/text colors                            | Scheme 1 |
| Full width           | Stretch the background edge-to-edge               | On       |
| Padding top / bottom | 0–100px                                           | 40 / 52  |

## Blocks

You can stack up to 3 of each text block and 2 button blocks:

* **Heading** (up to 3) — inline rich text + size (Small → Extra extra large)
* **Caption** (up to 3) — kicker line; style Subtitle or Uppercase; size Small/Medium/Large
* **Text** (up to 3) — rich text paragraph
* **Buttons** (up to 2 blocks, each with 2 buttons) — Button 1: label / link / outline toggle; Button 2: label (blank = hidden) / link / outline toggle

💡 **Pro tip:** Caption + big heading + one button is the highest-impact combo: `SPRING '26` / **"NOTHING HERE IS RESTOCKED"** / \[Shop the drop]. Keep it to one idea per band.


---

# 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://sitesbyseth.gitbook.io/sitesbyseth-docs/reign/sections/rich-text.md?ask=<question>&goal=<endgoal>
```

`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.