> 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/header/mobile-menu/blocks/button.md).

# Button

The button block lets you add a call-to-action button within the mobile menu: 

<figure><img src="https://content.gitbook.com/content/sD7BEEDU3B7WiEJlN0F7/blobs/v9Ri2WaYQyx8ShrbLFlA/button-gray.jpg" alt=""><figcaption></figcaption></figure>

Configure the block settings to customize the target link and text. Change the color, style, layout and spacing:

<figure><img src="https://content.gitbook.com/content/sD7BEEDU3B7WiEJlN0F7/blobs/bbS9Zvf1coe2VA5mNNtT/button-settings.jpg" alt=""><figcaption><p>Button block settings</p></figcaption></figure>

### What is Pin to bottom?&#x20;

When you activate "Pin to bottom" in the block settings, the block will remain sticky at the bottom of the mobile menu, allowing customers to have quick access during scrolling:&#x20;

<figure><img src="https://content.gitbook.com/content/sD7BEEDU3B7WiEJlN0F7/blobs/zLeeh4sDY1xAVyx8SFDZ/pin%20to%20the%20bottom.gif" alt=""><figcaption><p><strong>The Button block remains pinned to the bottom on scroll</strong></p></figcaption></figure>

## Block settings

<table><thead><tr><th width="148.14495849609375">Settings</th><th width="110.5928955078125" align="center">Type</th><th>Description</th></tr></thead><tbody><tr><td>Text</td><td align="center"><code>text</code></td><td>Button label.</td></tr><tr><td>Link</td><td align="center"><code>url</code></td><td>Link the button.</td></tr><tr><td>Color</td><td align="center"><code>select</code></td><td>Choose color style: <code>Primary</code>, <code>Black</code>, <code>White</code>, or <code>Secondary</code>.</td></tr><tr><td>Size</td><td align="center"><code>select</code></td><td>Choose button size: <code>Small</code>, <code>Medium</code>, or <code>Large</code>.</td></tr><tr><td>Style</td><td align="center"><code>select</code></td><td>Choose button style: <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>Display arrow icon.</td></tr><tr><td><strong>Layout</strong></td><td align="center"></td><td></td></tr><tr><td>Pin to bottom</td><td align="center"><code>checkbox</code></td><td>Pin the block to the bottom.</td></tr><tr><td><strong>Block spacing</strong></td><td align="center"></td><td></td></tr><tr><td>Padding bottom</td><td align="center"><code>range</code></td><td>Adjust bottom padding.</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/header/mobile-menu/blocks/button.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.