> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/frequently-asked-questions/how-do-i-add-text-dropdowns-to-my-map-overview.md).

# How do I add text dropdowns to my map overview?

Text dropdowns are a great way to condense large texts or different types of information in your [map overview](/overview/user-interfaces/map-editor.md#side-panel). Simply click on the dropdown-arrow to reveal more information:

<figure><img src="/files/RwxQSnFqLOkTrtz6mUFk" alt=""><figcaption></figcaption></figure>

To create them, add the following code to your map overview:&#x20;

```
<details> 
<summary> Text that should be visible at all times goes here </summary> 
Text that shows up after clicking the arrow shows up here.  
</details> 
```

Note that you can use as many of these blocks as you wish, to create different sections:

```
<details>
<summary> What are citrus fruits? </summary> 
Here are some examples:
1. Lemon 
2. Oranges 
3. Grapefruit 
</details>

<details> 
<summary> Countries commonly ranked "happiest in the world": </summary>  
- Denmark 
- Costa Rica 
- Australia 
</details>
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kumu.io/frequently-asked-questions/how-do-i-add-text-dropdowns-to-my-map-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.