> For the complete documentation index, see [llms.txt](https://pipeline.groupthought.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pipeline.groupthought.com/sections/list-of-sections/rich-text.md). # Rich text More than just text, loaded with icons, lists, and image blocks Build beautiful text-based headings or quickly create sections with icons, lists, or images. Rich text is a Pipeline's powerful multipurpose section with a wide range of blocks. Examples of blocks used with the Rich text section: ### Heading Add a custom heading to introduce the next section below:

### Icons Add the Icons block to build a quick row of rich SVG icons with text:

Use the block settings to choose from a large list of professionally designed premade icons, or add your own image. Additional settings to set the size of the text labels, background color, and more:

### Icons with text Another icon-based block with additional text and position-style options:

### Text and Image blocks Combine the text and image blocks to build custom logo promotions:

### Blocks Add blocks to customize the Rich text section and use on any page or template:

List of blocks included in Rich Text:


Kicker	Styled sub-heading
Heading	Main Pipeline heading style
Text	Description text
Buttons	Call to action buttons
Icons	Row of SVG icons with labels
Icons with text	SVG icons with robust text options
List	Order and unorder lists
Image	Display a custom logo or image
Spacer	Add a line or space between blocks

--- # 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://pipeline.groupthought.com/sections/list-of-sections/rich-text.md?ask=&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.