> 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/collections/collection-links-spotlight/collection.md).

# Collection

Each block represents a featured collection, allowing you to customize its title, image, button, and background color for a visually engaging spotlight layout.

{% hint style="warning" %}
**Limit:** Up to **5 blocks** per section.
{% endhint %}

<table><thead><tr><th width="160.38885498046875">Settings</th><th width="147.29681396484375" align="center">Type</th><th>Description</th></tr></thead><tbody><tr><td>Collection</td><td align="center"><code>collection</code></td><td>Select the collection to display.</td></tr><tr><td>Image</td><td align="center"><code>image_picker</code></td><td>Optional image to represent the collection.</td></tr><tr><td><strong>Typography</strong></td><td align="center"></td><td></td></tr><tr><td>Heading</td><td align="center"><code>text</code></td><td>Title for the collection block.</td></tr><tr><td>Heading size</td><td align="center"><code>select</code></td><td>Font size for the collection heading: <code>Mini</code>, <code>Extra small</code>, <code>Small</code>, <code>Medium</code>, <code>Large</code>, or <code>Extra large</code>.</td></tr><tr><td><strong>Button</strong></td><td align="center"></td><td></td></tr><tr><td>Text</td><td align="center"><code>text</code></td><td>Text for the button (mobile only).</td></tr><tr><td>Link</td><td align="center"><code>url</code></td><td>Destination link for the button.</td></tr><tr><td>Color</td><td align="center"><code>select</code></td><td>Button color options: <code>Primary</code>, <code>Secondary</code>, <code>White</code>, or <code>Black</code>.</td></tr><tr><td>Size</td><td align="center"><code>select</code></td><td>Button size options: <code>Small</code>, <code>Medium</code>, or <code>Large</code>.</td></tr><tr><td>Style</td><td align="center"><code>select</code></td><td>Button style options: <code>Solid</code>, <code>Outline</code>, or <code>Text</code>.</td></tr><tr><td>Show arrow</td><td align="center"><code>checkbox</code></td><td>Option to display an arrow icon in the button.</td></tr><tr><td><strong>Colors</strong></td><td align="center"></td><td></td></tr><tr><td>Background color</td><td align="center"><code>color</code></td><td>Background color for the collection block.</td></tr></tbody></table>


---

# 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/collections/collection-links-spotlight/collection.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.