> 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-collections.md).

# Featured collections

Show a row of collection cards in Avante. Fill it from the Collections setting or from Collection blocks — and know which one wins.

Featured collections is the quick way to build a category row: pick a few collections and the section renders a card for each one. Reach for it when you want navigation without art direction — the collection images carry the look.

### How to add

{% stepper %}
{% step %}

#### Add the section

In the theme editor click **Add section**, then pick **Featured collections**.
{% endstep %}

{% step %}

#### Choose how to fill it

Either pick collections in the **Collections** setting, or add one **Collection** block per card. Pick one — the two do not combine.
{% endstep %}

{% step %}

#### Set the layout

**Desktop style** and **Max columns number** decide how the cards sit on desktop. **Media ratio** and **Corner radius** apply to every card.
{% endstep %}
{% endstepper %}

### Good to know

**The Collections setting silently overrides the blocks.** As soon as **Collections** holds at least one collection, the section renders that list and ignores every Collection block. The blocks stay visible in the editor, so it looks like they are still in play — they simply never reach the storefront. The setting spells it out: *If this setting is filled, the section blocks will be ignored.*

To go back to blocks, clear the **Collections** setting completely. Removing all but one collection is not enough.

**Only blocks can carry a custom image.** The **Collections** list always uses each collection's own image. If you want campaign photography on the cards, build the section out of blocks.

{% hint style="info" %}
The **Collections** setting is the faster build and it reorders cleanly — drag a collection and the cards follow. Blocks are worth the extra clicks only when the images need art direction.
{% endhint %}

### Customization ideas

* Lay the page out with the **Collections** setting first, then switch to blocks once the photography arrives.
* Turn **Show frame** off for a flat, editorial look where the images sit straight on the page background.
* Drop **Max columns number** on a short list so the cards stay large instead of stretching thin.

***

### Related

* [Featured collection grid](https://staylime.com/docs/avante-themes/sections/collections/featured-collection-grid.md)
* [Featured collection with product grid](https://staylime.com/docs/avante-themes/sections/collections/featured-collection-with-product-grid.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-collections.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.
