> 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-columns.md). # Rich text columns Display text content in two columns with easy position controls Broadcast includes a quick, easy-to-use section for building text content into a customized two-column layout. We include columns that can be sized differently and blocks easily positioned to either column.

An example of rich text with columns section with 40% and 60% sized columns — **Leading section is Rich text with columns. 40% and 60% sized columns**

### Section settings Content can be moved easily from one column to another. The content will appear stacked on mobile devices with either centred or left alignment.

Settings	Type	Description
Left column
Width	`range`	Width of the left column on desktop.
Divider
Width	`range`	Width of the divider between columns.
Show line	`checkbox`	Toggle to display the vertical dividing line.
Right column
Width	`range`	Width of the right column on desktop.
Text alignment	`select`	Aligns text in the right column. Options: `Left`, or `Right`.
Layout
Width	`select`	Sets total section width. Options: `Full width padded`, `Normal`, or `Narrow`.
Mobile
Text alignment	`select`	Text alignment on mobile. Options: `Left`, or `Center`.
Colors
Color scheme	`color_scheme`	Select a color scheme.
Padding
Top	`range`	Padding above section content.
Bottom	`range`	Padding below section content.

### Video Overview This video demonstrates the section settings and block options for the **Rich text columns** section, including left and right placement of content: {% embed url="" %} **Video walkthrough of the rich text with columns 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-columns.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.