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

# Rich text

The **Rich text** block is the main block for **formatted text**: paragraphs, headings, lists, links, bold, italic, and similar.

***

## What you can do

* Write and format **body copy** with headings, lists, and links.
* Use it as the **heading** inside other blocks (e.g. Lead form, Instagram feed, FAQ) when the block allows a "heading" slot.
* Style text using the editor toolbar (bold, italic, lists, etc.); exact options depend on your StoryPress setup.

***

## How it works

You type or paste text into the rich-text editor. The block stores both the text and the formatting. On the live site it renders as HTML that matches your theme's typography.

***

## Tips

* Use **headings** (e.g. H2, H3) to structure long content so it's easier to scan and better for accessibility.
* Keep paragraphs short on the web; use bullet lists where they make sense.


---

# 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://storypress.gitbook.io/storypress-docs/content-blocks/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.