> For the complete documentation index, see [llms.txt](https://docs.ultramarinastudios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ultramarinastudios.com/templates/collection-list.md).

# Collection list

The collection list template outputs a complete list of collections on your site.

<figure><img src="https://3146423938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZQuVfmt0J7tzTvfBqG6C%2Fuploads%2FvefxNSFFe2D4fNtrUrlb%2Fcollection-list.png?alt=media&amp;token=0159b131-06a3-45a6-9859-3cbe89f28cc3" alt="A title, &#x27;Collections (6)&#x27;, with Bestsellers, Chairs, and Decor in a three column grid."><figcaption><p>The collections list section from the Composition preset.</p></figcaption></figure>

{% hint style="info" %}
You can set a consistent image ratio for collection cards in [Theme settings > Collection card](https://docs.ultramarinastudios.com/theme-settings/collection-card.md).
{% endhint %}

### Settings

* **Collections:** By default all collections will be listed on this page. However, if you are using some collections for organizational purposes or apps, you may not wish for customers to see these collections. You could use this setting to output a list of collections that are appropriate for customers to see.
* **Desktop/mobile columns:** Choose the number of columns on mobile and on desktop.
* **Horizontal alignment**: Applies to the collection titles specifically

### Blocks

This section also comes with pre-loaded with a [Section header](https://docs.ultramarinastudios.com/blocks/section-blocks/section-header.md) block.

{% hint style="info" %}
Can't find the setting you're looking for?  The following settings are explained in detail in common settings:&#x20;

* Container type
* Color scheme/Color scheme transition
* Padding
* Borders
  {% endhint %}


---

# 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://docs.ultramarinastudios.com/templates/collection-list.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.
