> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/content-management/explorations-section.md).
# Explorations Section
## What is an Exploration Section?
An exploration section helps you organize exploration in a comprehensive way that makes sense for your company. By default, your organization has two sections:
* :star: **General**\
Where exploration that are live are stored, this is visible by any users who have access to explorations
* :tools: **Work in Progress**\
Where you can store exploration that are not live yet, only builders and more view exploration stored here
## Create a section
in order to create an exploration section, click on **Explore**, then click on the **+ button** and then on **New Section**.
Create an exploration
You can give your section a name and an icon.
## Move a section
You can move sections around to change your company explorations structure, this will update to all users in real time.
Move a section
## Update / Delete a section
By clicking on the three dots next to a section's name you can update or delete a section.
Update / delete a section
{% hint style="warning" %}
You can't delete a section with exploration in it. You need to move them or delete them before hands.
{% endhint %}
---
# 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://docs.whaly.io/content-management/explorations-section.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.
