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

# Featured collection

A product grid pulled from any collection — the workhorse of the homepage.

**Where to use it:** the homepage (it ships there by default), landing pages, or anywhere you want to surface a specific set of products.

## Settings

* **Heading** (default "Featured") — the title above the grid. Leave empty for a cleaner look.
* **Collection** — which collection to show. If none is selected, placeholder products render in the editor so you can see the layout.
* **Products to show** (2–12, default 8).
* **Columns on desktop** (2–6, default 4) — 4 columns × 8 products = two clean rows.
* **Columns on mobile** — **1** or **2** (default).
* **Show view all link** (on by default) — a link to the full collection beneath the grid. Useful when the collection holds more products than you're showing.

### Section style

* **Top padding** / **Bottom padding** (0–120 px, default 64), **Background color**, **Text color**.

## No blocks

This section has no blocks — the cards come straight from the collection. The card design (aspect ratio, crop, hover image, quick view +, badges) is global: **Theme settings → Product cards** (see [Theme settings](/sitesbyseth-docs/skeleton/theme-settings.md)).

💡 **Pro tip:** create a dedicated collection just for this section (e.g. "Homepage picks") and hand-sort it under **Products → Collections → your collection → Sort: Manually**. That way your homepage always leads with your best sellers and freshest drop, independent of how the rest of your catalog is organized.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sitesbyseth.gitbook.io/sitesbyseth-docs/skeleton/sections/featured-collection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.