> 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/volume-themes/sections/products/featured-products-featured-collections-and-featured-collection-grid.md).
# Featured Products, Featured Collections & Featured Collection Grid
Volume's Featured Products, Featured Collections, and Featured Collection Grid sections showcase a curated set of products or collections as a grid or slider.
Three ways to put a curated set of products or collections front and center — as a grid or a swipeable slider — perfect for bestsellers, new arrivals, or a seasonal edit.
* **Featured Products** — hand-pick individual products.
* **Featured Collections** — hand-pick whole collections, each shown as a tile.
* **Featured Collection Grid** — the tighter, grid-only version of Featured Collections.
***
### Featured Products
#### How to add
In the Theme Editor, click **Add section** → **Featured products**, then pick your products in **Product list**. Choose **Grid** for a paginated layout, or **Slider** for a swipeable row.
#### Good to know
* Grid and Slider are two different layouts, not a responsive switch — pick the one that fits how many products you're featuring.
* The optional **Information card** can sit first or last in the row, so it can work as either a section intro or a closing "shop the edit" CTA.
* Product card settings (hover behavior, quick buy, price position, vendor, badges) are the same shared component used by Featured Collections, Product Recommendations, and Recently Viewed — set them once, they'll look consistent everywhere.
#### Customization ideas
* Set the Information card to appear first and link it to your best-selling collection, so the section doubles as a "shop more" prompt.
* Switch to Slider once you're featuring more than 8–10 products — Grid's pagination gets busy at that count.
#### Settings
Settings
| Setting | What it does |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Product list | Manually pick the products to display |
| Layout | Grid (paginated) or Slider (swipeable) |
| Products per page / Columns | Grid mode only |
| Desktop item width | Slider mode only — controls how many products show at once |
| Arrows / Scrollbar | Slider navigation controls |
| Information card | Optional promo tile (image/video, overlay, heading, text, button) inserted first or last among the products |
| Product card settings | Hover image swap, quick buy, vendor, price position, badges — shared across every product-grid section in the theme |
***
### Featured Collections
#### How to add
In the Theme Editor, click **Add section** → **Featured collections**, then **Add block** → **Collection** for each collection you want to feature.
#### Good to know
* Each collection block can override its image independently via **Custom collection image** — useful when a collection's default image doesn't crop well at this section's aspect ratio.
#### Customization ideas
* Use the slider layout once you're featuring 5+ collections so nothing feels cramped.
#### Settings
Settings
| Setting | What it does |
| ----------------------- | ----------------------------------------------------- |
| Collection blocks | One block per featured collection |
| Custom collection image | Per-block override for the collection's default image |
| Layout | Grid or Slider |
| Information card | Optional promo block, same as Featured Products |
***
### Featured Collection Grid
#### How to add
In the Theme Editor, click **Add section** → **Featured collection grid**, then **Add block** → **Collection** for each collection you want to feature.
#### Good to know
* This is the tighter, grid-only sibling of Featured Collections — no slider option, and grid gaps are off by default for a denser look.
#### Customization ideas
* Use this instead of Featured Collections for a tight, curated set of 3–4 collections.
#### Settings
Settings
| Setting | What it does |
| ----------------- | ---------------------------------------------------------------------- |
| Collection blocks | One block per featured collection, with the same custom-image override |
| Grid style | Defaults to the "alternative" style |
| Disable grid gaps | On by default — remove for a looser, spaced-out grid |
### Best practices
* Reach for Featured Products when you need exact product-level control; reach for Featured Collections or Featured Collection Grid when the curation should live at the collection level instead.
* Keep Layout and card settings consistent with other product sections on the same page so the shopping experience feels uniform.
### Related
* [Featured product](/docs/volume-themes/sections/products/featured-product.md)
* [Product with text & featured collection with media](/docs/volume-themes/sections/products/product-with-text-and-featured-collection-with-media.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/volume-themes/sections/products/featured-products-featured-collections-and-featured-collection-grid.md?ask=&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.