> For the complete documentation index, see [llms.txt](https://docs.beefree.io/beefree-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beefree.io/beefree-sdk/~/changes/463/other-customizations/extend-title-block-with-h4-h5-and-h6.md).

# Extend Title Block with H4, H5, and H6

{% hint style="info" %}
Available on all Beefree SDK builder and [plans](https://developers.beefree.io/pricing-plans).
{% endhint %}

## Overview

The Title Block supports H4, H5, and H6 headers in addition to the existing H1–H3 options. This enhancement gives end users more flexibility to structure content with proper semantic hierarchy, improving both accessibility and readability.

## How to Activate the Feature

By default, the builder's [Title Block ](https://docs.beefree.io/end-user-guide/content-blocks/titles)will display only H1–H3. To enable additional heading levels, you need to add the `titleMaxLevel` parameter to your configuration. Ensure you set it to the maximum value you'd like to make available in the builder. For example, `h6` will allow your end users to select H1, H2, H3, H4, H5, or H6 from the drop down menu within the Title Block.

Example configuration:

```js
beeConfig: {
  titleDefaultConfig: {...},
  titleDefaultStyles: {...},
  titleMaxLevel: 'h6' // 'h3' default (min 'h1', max 'h6')
}
```

* If not set, the default value is **h3**.
* You can allow up to a specific level (for example, `h4`) or all the way to `h6`.

Here’s what the editor experience looks like if `titleMaxLevel` is set to **h4**:

<figure><img src="https://806400411-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8c7XIQHfAtM23Dp3ozIC%2Fuploads%2FzXyxSWjuRkpmCCX4WM51%2FCleanShot%202025-08-19%20at%2019.22.33%402x.png?alt=media&amp;token=46597aa7-12d5-4518-a219-05ab0977cde7" alt=""><figcaption></figcaption></figure>

## Default Styles for H4–H6

Just like H1–H3, you can define [Content Default](https://docs.beefree.io/beefree-sdk/~/changes/463/other-customizations/appearance/content-defaults.md#content-defaults-for-additional-title-levels) styles for H4–H6 under `titleDefaultStyles`:

```js
beeConfig: {
  titleDefaultStyles: {
    h4: {
      color: 'red',
      'font-size': '13px',
      'font-family': 'Arial, sans-serif',
      'font-weight': '700',
      'link-color': 'blue',
      'line-height': '120%',
      'text-align': 'center',
      'direction': 'ltr',
      'letter-spacing': 0,
    },
    h5: {
      color: 'black',
      'font-size': '12px',
      'font-family': 'Arial, sans-serif',
      'font-weight': '700',
      'link-color': 'blue',
      'line-height': '120%',
      'text-align': 'center',
      'direction': 'ltr',
      'letter-spacing': 0,
    },
    h6: {...}
  },
}
```

## Additional Considerations

Consider the following when adding header options:

* **Granularity**: This configuration allows enabling headings per UID, giving you control over which end users see them.
* **Customizability**: You can define distinct styling for each heading level to match brand guidelines using [Content Defaults](https://docs.beefree.io/beefree-sdk/~/changes/463/other-customizations/appearance/content-defaults.md#content-defaults-for-additional-title-levels).


---

# 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.beefree.io/beefree-sdk/~/changes/463/other-customizations/extend-title-block-with-h4-h5-and-h6.md?ask=<question>&goal=<user_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.
