> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/space/sections/content-and-media/blog-posts-grid.md).

# Blog posts grid

### Section overview

The Article Grid section displays a collection of blog articles in a customizable grid layout, ideal for showcasing recent or featured content throughout your store.

#### Common use cases

* Highlighting recent blog posts on your homepage
* Creating a featured articles section on collection pages
* Showcasing curated content on landing pages
* Building a blog index page with flexible layout options

#### Usage tips

* Keep the number of displayed articles balanced with your layout (3-6 articles work well for most designs)
* Use concise, compelling headings to introduce your article grid
* Consider using the split layout option for blog-focused pages to keep header content visible
* Adjust column count for mobile to ensure readability (single column is recommended)

### Section settings

| Setting              | Description                                                |
| -------------------- | ---------------------------------------------------------- |
| Blog                 | Select which blog to display articles from                 |
| Total items          | Number of articles to display in the grid                  |
| Heading              | Main heading text for the section                          |
| Content              | Descriptive text that appears above the article grid       |
| Button label         | Text for the optional call-to-action button                |
| Button url           | URL destination for the call-to-action button              |
| Top spacing          | Amount of space (in pixels) above the section              |
| Bottom spacing       | Amount of space (in pixels) below the section              |
| Color scheme         | Select from theme color schemes for the section background |
| Custom color         | Set a custom background color (when 'Custom' is selected)  |
| Text color           | Choose between default, light, or dark text color          |
| Border color         | Select subtle or strong border color                       |
| Button color         | Choose from various button style options                   |
| Enable color fade    | Enables smooth color transitions between sections          |
| Border position      | Choose where borders appear (top, bottom, both, or none)   |
| Desktop columns      | Number of columns to display on desktop (1-8)              |
| Mobile columns       | Number of columns to display on mobile (1-3)               |
| Horizontal alignment | Set content alignment (left, center, or right)             |
| Enable margin        | Apply horizontal margin to the section content             |
| Enable split         | Divide the section into a sidebar and main content area    |
| Enable split heading | Keep the heading in its own column separate from content   |
| Visibility           | Control section visibility on different device types       |

### Block settings

This section does not contain any blocks.

Search files...

Search files...


---

# 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://help.brickspacelab.com/space/sections/content-and-media/blog-posts-grid.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.