> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/sections/sections/advanced/custom-section/collection.md). # Collection Highlights a product collection, allowing visitors to browse grouped items directly from the section.

Design of two collection blocks side by side

{% hint style="warning" %} You can only choose two blocks to be shown at a time. {% endhint %}

Settings	Type	Description
Collection	`collection`	Choose a Shopify collection to feature in this section.
Typography
Heading	`text`	Enter a title or heading for the collection section.
Colors
Background	`color`	Set the background color of the section.
Text	`color`	Set the color of the text content.

--- # 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://broadcast.presidiocreative.com/sections/sections/advanced/custom-section/collection.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.