> For the complete documentation index, see [llms.txt](https://docs.ultramarinastudios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ultramarinastudios.com/sections/section-header.md). # Section header The section header is not meant to be a standalone section. Rather, it is meant to be combined with any other section to create a heading.

### Settings * **Layout**: Choose between a **left-aligned** or a **centered** layout * **Text content**: * **Subheading** * **Heading** * [Set as page title](/common-settings.md#set-as-page-title) * **Heading size** * **Count (optional)**: If heading accents are enabled, gives users a sense of how many items are in the section * **Text** * **Button label** and **link** {% hint style="info" %} Can't find the setting you're looking for? The following settings are explained in detail in [common settings](/common-settings.md): * Color scheme/Color scheme transition * Padding * Borders {% endhint %} {% hint style="info" %} Tip: Decrease the bottom padding to visually connect the section header to the content below it! {% endhint %} ### Examples & inspiration

Create a custom product header by adding the title and description as dynamic sources.

### Similar sections


The rich text columns section allows you to add any content within two equal columns for greater flexibility.	Primavera Gloss 2025-04-02 at 5.07.07 pm.jpg

--- # 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://docs.ultramarinastudios.com/sections/section-header.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.