> 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/showcase/sections/rich-text.md).

# Rich text

A clean column of headings, text, and buttons — no imagery. The quiet workhorse for manifestos, policies-in-brief, or an intro paragraph between sections.

👉 **Customize → Add section → Rich text** (on pages that allow sections).

## Settings

* **Alignment** — left / center (default) / right text alignment.
* **Max content width** (400–1200px, default 700px) — how wide the column can get. Narrower reads better for long text.

## Blocks

Add any number, in any order:

### Heading

* **Heading** (default "Talk about your brand").

### Text

* **Text** (rich text, default "Share information about your brand with your customers.").

### Button

* **Label** (default "Learn more") + **Link** — outline style; empty label hides it.

## Pro tip

💡 A single centered Heading block, max width 700, no text, makes a great typographic divider between heavier sections — especially in the Luxury font style where the Marcellus serif carries a line on its own.


---

# 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/showcase/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.