> 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/paper/sections/products-and-collections/featured-product.md).

# Featured product

### Section overview

The Featured Products section displays a customizable grid of highlighted products with multiple images from a selected collection.

#### Common use cases

* Showcase bestselling or seasonal products on the homepage
* Feature new arrivals in a visually appealing grid layout
* Highlight products with special promotions or discounts
* Create curated product collections for specific customer segments

#### Usage tips

* Select products with at least 4 high-quality product photos for the best visual presentation
* Customize the grid layout based on your store design (2-4 columns for desktop, 1-2 for mobile)
* Use consistent product photography style for a cohesive look
* Balance the number of featured products with page load times for optimal performance
* Test different color schemes and border styles to match your brand aesthetic
* Ensure product titles and details are clearly visible on mobile devices

### Section settings

| Setting           | Description                                                                            |
| ----------------- | -------------------------------------------------------------------------------------- |
| Collection        | The product collection to display in the grid                                          |
| Total items       | The maximum number of products to display (default: 3)                                 |
| Heading           | The title text for the section                                                         |
| Content           | Descriptive text for the section (supports rich text formatting)                       |
| Button label      | Text to display on the section's call-to-action button                                 |
| Button URL        | The destination URL when the button is clicked                                         |
| Spacing top       | Amount of vertical space above the section (0-300px, default: 100px)                   |
| Spacing bottom    | Amount of vertical space below the section (0-300px, default: 100px)                   |
| Color scheme      | Background and text color combination for the section                                  |
| Border color      | Color of section borders (subtle or strong)                                            |
| Button color      | Color style for the section's button (primary, secondary, tertiary, neutral, or plain) |
| Border position   | Position of section borders (none, top, bottom, or both)                               |
| Desktop columns   | Number of product columns on desktop devices (2-4, default: 3)                         |
| Mobile columns    | Number of product columns on mobile devices (1-2, default: 1)                          |
| Content alignment | Horizontal alignment of section content (left, center, or right)                       |
| Visibility        | Device visibility options (all devices, mobile only, or desktop only)                  |

### Block settings

This section does not contain any customizable blocks.


---

# 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/paper/sections/products-and-collections/featured-product.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.