> 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/showcase/sections/main-collection.md).

# Collection page

Renders a collection as the full-screen story experience — every product in the collection gets a screen, in the collection's sort order, with **one shared background** behind them all and the auto-numbered side rail down the edge. Long collections paginate with Previous/Next buttons after the last screen; empty collections fall back to a simple "No products found" page.

👉 **Customize → page selector → Collections → Default collection → Collection page** section. Walkthrough: [The collection page](/sitesbyseth-docs/showcase/getting-started/collection-page.md).

## Settings

### Experience

* **Products per page** (3–16, default 8) — screens per page before pagination.
* **Product transition** — `Fade (no sliding)` (default) or `Scroll`. Fade needs 2+ products on the page.
* **Show scroll hint on first screen** (on).
* **Slideshow navigation** — `Arrows` (default), `Dots`, `Arrows and dots`, or `None (swipe only)`.
* **Show product image slideshow** (on) — untick for a background-led, imageless look.
* **Auto-remove studio background** (off) — cutout for every product's photos on this page; unsuitable photos are skipped automatically. See [Auto-cutout](/sitesbyseth-docs/showcase/auto-cutout.md).
* **Show description under the title** (off) — trimmed product description under each name.
* **Info style** — `Transparent` (default) or `Glass panel`.

### Background (shared by every product screen)

Rendered once and fixed behind all products — a video loads and plays exactly once for the whole page.

* **Background video** — wins over the image.
* **Background image** — used when no video is set.
* **Background color** (default `#F3F0EA`) — used when neither is set.
* **Overlay darkness** (0–90%, default 35%).
* **Text color** — `Auto` (light over media, dark on color), `Light`, or `Dark`.

### Buy now

* **Show Buy now button** (off by default here) — skips the cart, straight to checkout. No offer product on the collection page — offers are a homepage/product-page feature.

### Find my size

Appears automatically on clothing products. **How do these pieces fit?** and **Garment type** apply to *all* products on this page — if your collection mixes cuts, keep these at the defaults (`True to size`, `Top / tee / hoodie`) and set per-piece profiles on homepage story blocks and the product page instead. Guide: [Size finder](/sitesbyseth-docs/showcase/size-finder.md).

### Accordions

* **Show description accordion** (on).
* **Shipping timeline title** (default "Shipping timeline") + **content** — one shipping accordion shown on every product screen; renders only when content is filled.

## Pro tip

💡 Give each collection its own mood by duplicating the template: **page selector → Collections → Create template**, set a different shared background per template, then assign collections to templates from their admin pages. A "Drop 03" collection with its own campaign-video background feels like a dedicated microsite.


---

# 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/showcase/sections/main-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.