# Heading

Renders text as a heading. Choose a visual size (XS through XXXL), an HTML level (H1–H6) for semantics, and an alignment.

The visual size is independent of the HTML level — you can use a small visual heading at H2 for semantic depth without making it look huge.

## Available in

* Page modules
* Order Form modules
* Catalog modules
* Dashboard modules
* Public Page modules

Heading isn't available in Modal, Reports, or Navigation modules.

## When to use

* Every page should have a single H1 — typically a Heading at the top.
* Section dividers (H2 / H3) inside a page.
* Card titles where the Card block's built-in title isn't flexible enough.

## Settings

| Setting   | Description                                                                                                                    |
| --------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Text**  | The heading content. Multi-line.                                                                                               |
| **Size**  | Visual size: XXXL, XXL, XL, L, M, S, XS. Default: M.                                                                           |
| **Level** | HTML semantic level: H1–H6, or none (renders as a div). Pick H1 for the page's main heading, H2 for major sections, and so on. |
| **Align** | Left, Center, Right. Default: Left.                                                                                            |

## How it works

The HTML output uses the configured Level (e.g. `<h1>` for level 1). The Size setting controls the font size via CSS, independent of the level — so a level 2 heading can be as small or large as you want visually.

The Align setting controls text alignment within the block.

{% hint style="info" %}
Use level **H1 once per page** for the page title, then H2 for major sections, H3 below those. Consistent levels improve accessibility (screen readers use them) and SEO.
{% endhint %}

## Examples

**Page title.** Heading with text *Sales Reports*, size XXL, level H1, alignment Left.

**Section divider.** Heading with text *Today's Activity*, size L, level H2.

**Card title alternative.** Inside a Column, a Heading with size M, level H3, alignment Center, used as a section header above a Stats grid.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Text</strong></td><td>Body text and descriptions.</td><td><a href="/pages/3PTXn8qiRmeAo7cULvFI">/pages/3PTXn8qiRmeAo7cULvFI</a></td></tr><tr><td><strong>Hero</strong></td><td>For big landing-page-style headings with a button.</td><td><a href="/pages/oLF0GvowbgafCiW5QGv6">/pages/oLF0GvowbgafCiW5QGv6</a></td></tr><tr><td><strong>Best Practices</strong></td><td>Heading hierarchy and accessibility tips.</td><td><a href="/pages/vAbsWdSLiwdLsG7BZSoq">/pages/vAbsWdSLiwdLsG7BZSoq</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/content-components/heading.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.