> 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-with-media.md).

# Featured collection with media

Pair one collection with a large image or video in Avante, and choose between collection order and a random starting point.

Featured collection with media sits a large visual next to a small product grid. It is the section for a story with something to buy attached: the lookbook shot on one side, a few products from the matching collection on the other.

### How to add

{% stepper %}
{% step %}

#### Add the section

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

{% step %}

#### Pick the collection

The products come from one **Collection**.
{% endstep %}

{% step %}

#### Add the media

Upload a **Video** or a **Custom image**. **Swap image position** moves it to the other side, **Image size** sets how much room it takes.
{% endstep %}

{% step %}

#### Add the button

**Button label** leads to the collection page. Leave it empty to hide the button.
{% endstep %}
{% endstepper %}

### Good to know

**The media follows a priority order.** **Video** wins over **Custom image**, and the collection's own image is used only when both are empty. **Enable pause control** and **Enable mute control** appear only once a video is uploaded.

**Random is not a shuffle.** With **Products order** set to **Random**, the theme picks a random *starting point* in the collection and takes the products that follow it, in order. You get a contiguous slice, so products that sit next to each other in the collection still appear together.

**Random is recalculated on every render.** The starting point comes from the clock at the moment the page is built, so the section changes between visits and between shoppers. That is the point of it — but it also means you cannot preview what people will see.

{% hint style="info" %}
The section reads the collection without pagination, so it only ever sees the **first 50 products** of the collection's current sort order. A random starting point lands inside that fifty, not across the whole catalogue. On a long collection, sort it in the Shopify admin so the fifty you want are the ones at the top.
{% endhint %}

**A short collection always starts at the top.** When the collection holds no more products than the grid shows, the starting point is forced to zero and **Random** behaves exactly like **Collection**.

**Products order set to Collection is the predictable one.** It starts at the top every time and respects the sort order you set in Shopify.

### Customization ideas

* **Random** on a large evergreen collection keeps a home page feeling alive without anyone editing it.
* **Collection** order with a manual sort, for a curated story where the first product has to be the hero.
* Alternate **Swap image position** between two consecutive sections so the page zigzags instead of lining up.

***

### Related

* [Collection with sticky image](https://staylime.com/docs/avante-themes/sections/collections/collection-with-sticky-image.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-collection-with-media.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.
