From ab20c33cc1c05e9a9fd544d12544d7f91851728a Mon Sep 17 00:00:00 2001 From: Richard Towers Date: Wed, 4 Dec 2024 11:49:17 +0000 Subject: [PATCH] Document heading_level for heading blocks --- docs/building_blocks_for_flexible_content.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/building_blocks_for_flexible_content.md b/docs/building_blocks_for_flexible_content.md index 95d5a2d307..b98d9ace3a 100644 --- a/docs/building_blocks_for_flexible_content.md +++ b/docs/building_blocks_for_flexible_content.md @@ -121,12 +121,13 @@ When added through Whitehall content can either be written in HTML or govspeak m A wrapper around the [Heading component](https://components.publishing.service.gov.uk/component-guide/heading). This block uses `content` where the component uses `text` for the title text key. This is so that headings can appear in search (only values inside a `content` key will be indexed when being published from Whitehall - see [Indexing block content in search](#indexing-block-content-in-search)) -If an `id` is added, the heading can be referenced in an anchor link. +If an `id` is added, the heading can be referenced in an anchor link. `heading_level` can be used to specify the heading level (the default is 2) - you should usually have at least one `heading_level: 1` towards the beginning of a page's content. ```yaml - type: heading id: heading-id content: Porem ipsum dolor + heading_level: 3 ``` #### Image