> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/sections/collections/featured-collection-grid.md).

# Featured collection grid

Build a grid of collection tiles in Avante: one tile per collection, a sticky side column, custom images and product counts.

Featured collection grid gives shoppers a short list of places to start. Instead of dropping them straight into a wall of products, you show a handful of routes — Sale, New in, Gifts under $50 — and let them choose. It works well right under the hero on the home page, and on campaign landing pages that split into a few clear paths.

Every tile in this section is a **collection**, not a product. The tile shows the collection image and title, and links to the collection page.

### How to add

{% stepper %}
{% step %}

#### Add the section

In the theme editor, open the template you want and click **Add section**, then pick **Featured collection grid**.
{% endstep %}

{% step %}

#### Add one Collection block per tile

Each **Collection** block is one tile. Pick a collection inside the block. You can add up to **8** blocks.
{% endstep %}

{% step %}

#### Replace the image where it matters

A collection's own image is often just the first product photo, which rarely works as a category tile. Upload a **Custom image** in the block to override it.
{% endstep %}

{% step %}

#### Write the side column

The subheading, heading and button live in the section settings. Leave **Button label** empty to hide the button.
{% endstep %}
{% endstepper %}

### Good to know

**An empty block disappears.** A tile is only rendered when its block has a collection selected, so a half-finished block leaves no gap in the grid. You can add the block now and pick the collection once it is ready.

**Show product quantity counts everything.** The number next to the title is the collection's total product count. It ignores stock and any filters, so a collection of 40 products shows 40 even when half of them are sold out.

**Enable sticky content is on by default.** It pins the side column while the tiles scroll past it. You only see the effect when the tiles are taller than that column — with two or three tiles nothing appears to happen. **Offset** controls the gap the column keeps from the top of the page, which you will want to raise if your header is sticky too.

{% hint style="info" %}
All tiles share one **Image ratio**. Crop your custom images to that ratio before uploading, otherwise the theme crops them for you and the interesting part may be the part it cuts.
{% endhint %}

### Customization ideas

* Use it as a season switcher — one tile per drop, each with the campaign photo as the custom image.
* Turn **Show product quantity** off for curated edits, where a count of 6 undersells the selection.
* Keep the side column short: it is the one piece of copy that stays on screen while the tiles move.

***

### Related

* [Featured collections](https://staylime.com/docs/avante-themes/sections/collections/featured-collections.md)
* [Collection list with popover image](https://staylime.com/docs/avante-themes/sections/collections/collection-list-with-popover-image.md)
* [Collections](https://staylime.com/docs/avante-themes/sections/collections.md)


---

# 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://staylime.com/docs/avante-themes/sections/collections/featured-collection-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.
