> 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/broadcast-v3/sections/sidebar.md).

# Sidebar

FAQ style content with sidebar navigation

> Section introduced in Broadcast 3.2

Display accordion and text-based content in a section. Featuring autogenerated navigation that allows customers to navigate easily through your content blocks.&#x20;

The sidebar navigation is displayed on desktop devices and remains sticky for quick access to content areas.&#x20;

![](https://content.gitbook.com/content/gPVWISoa427RKoZWt1y6/blobs/tR8huI0TA3Jl4rnY5wqT/sidebar-section.png)

### How to use

View the complete overview of this section including adding blocks and section settings:

{% embed url="<https://www.loom.com/share/05ed4c73c5df453dbf8bcdd644bd4669>" %}

### Settings

This section includes sections settings and multiple block options:

<details>

<summary>Blocks</summary>

* **Header** (used to group and link to by dynamic sidebar navigation)
* **Accordion** (main question or title, always shown)
* **Text** (content within accordion, shown once expanded)

</details>

<details>

<summary>Section</summary>

* **Section width**
* **Colors** (background and text both support dynamic source)
* **Section padding** (top and bottom)

</details>

### Version

The Sidebar section was introduced in Broadcast 3.2.0&#x20;


---

# 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/broadcast-v3/sections/sidebar.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.
