> 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/blocks/heading.md).

# Heading

This block displays an <kbd>h2</kbd> heading with an optional subheading (or "eyebrow" text) above it:

<figure><img src="/files/FhxbpOUn5uFzmY17PFRm" alt=""><figcaption><p>Heading block on Gloss demo store</p></figcaption></figure>

### Settings

* **Set as page title:** For accessibility and SEO purposes, it is important to have one <kbd>h1</kbd> heading per page. This heading should represent the main title of page, for example, "Contact Us", "All products", etc. Checking this box will make the corresponding heading be an `<h1>`tag.<br>

  This setting has no effect on the visual styles of the heading, it only controls the underlying code.

### Nested blocks

* **Subheading**: Also known as an "eyebrow" text, this appears above headings in smaller font. The style of subheading can be adjusted under **Settings > Typography**. To omit a subheading, delete all the text within this text field or, if it's a block, delete the block.
* **Heading:**&#x20;
  * **Heading**: Enter the heading text
  * **Heading size**: Choose the visual style of the heading


---

# 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://docs.ultramarinastudios.com/blocks/heading.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.