> 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/collection-list.md).

# Collection list

A grid of category tiles — each one linking to a collection. The "shop by category" section.

**Where to use it:** the homepage, right after the hero, so visitors can self-sort into Tees / Hoodies / Accessories in one click.

## Settings

* **Heading** (default "Shop by category").
* **Columns on desktop** (2–6, default 3).
* **Columns on mobile** — **1** or **2** (default).

### Section style

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

## Blocks

### Collection (up to 12)

* **Collection** — pick the collection this tile links to. The tile uses the collection's featured image and title by default.
* **Custom image** — override the collection's image with your own. Use this to keep all tiles in one consistent photography style.
* **Custom title** — override the collection's name on the tile (e.g. show "HOODIES" instead of "Hoodies & Crewnecks FW26").

💡 **Pro tip:** give every collection a featured image (**Products → Collections → your collection → upload under Image**) in the same aspect ratio and style — a mismatched tile grid is the fastest way to make a store look amateur. Three to six tiles is the sweet spot; if you need twelve, your navigation menu should be doing more work.


---

# 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/collection-list.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.