# Content blocks

The content blocks section displays multiple structured content items in a grid layout. It is designed for showcasing grouped information such as features, services, or editorial highlights in a clean, organized format.

<figure><img src="/files/ZhVDcSqdhkHoo5BpeN5o" alt=""><figcaption></figcaption></figure>

#### Show header

Controls the visibility of the section header above the content blocks. When enabled, the heading and subheading are displayed if set.

#### Direction

Defines the layout direction on desktop. Set to “Row” to display blocks horizontally; mobile always uses a column layout for usability.

#### Heading

The main heading displayed for the section. Default is “Content blocks”. Leave blank to omit.

#### Subheading

Optional supporting text shown below the heading to provide additional context or explanation. Leave blank to omit.

#### Button label

Defines the text for an optional call-to-action button. Leave blank to hide the button.

#### Button link

Specifies the URL destination for the button. Can link to a page, collection, or external URL. Leave blank to omit.

#### Button style

Defines the visual style of the button. Default is “Secondary”.

#### Grid columns (desktop)

Sets the number of columns used to display content blocks on desktop. Default is 2, creating a balanced grid layout.

#### Vertical spacing

Controls the spacing around the section to adjust its separation from surrounding content.

#### Vertical spacing (desktop)

Sets the vertical spacing applied on desktop devices. Default is Large.

#### Vertical spacing (mobile)

Sets the vertical spacing applied on mobile devices to ensure consistent spacing across screen sizes.


---

# 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://gatame.gitbook.io/highstreet/dynamic-sections/editorial/content-blocks.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.