> For the complete documentation index, see [llms.txt](https://gitbook-v2-ddzba6384-gitbook.vercel.app/url/gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-v2-ddzba6384-gitbook.vercel.app/url/gitbook.com/docs/create-content/content-structure/collection.md).
# Groups
Organize related sections within your site
Section groups let you organize related sections within your site, making your site's structure easier for visitors to navigate.
Section groups are different from [Pages](/url/gitbook.com/docs/create-content/content-structure/page.md). Page groups organize pages within one section. Section groups organize sections in site navigation. Both are called groups, but you configure their icons independently.
### Create a group
1. In your site, click **Add…**.
2. Click **New group**.
3. Choose a title and an icon that represents the group.
New groups start as **drafts**: they aren't visible on your published site until you publish them.
### Add sections to a group
1. Open the **structure editor**.
2. Drag the section into or out of the group.
Or create a new section directly inside a group.
### Publish a group
1. Open the group's **Action menu** .
2. Click **Publish**.
Or publish several drafts at once from the structure editor.
To preview how draft groups look on your site, switch the site preview between **Live** and **Live + Drafts**.
### Rename a group
1. Click the **Action menu** icon next to the group.
2. Click **Rename**.
3. Change the group's title or icon.
### Delete a group
1. Open the group's **Action menu** .
2. Click **Delete**.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://gitbook-v2-ddzba6384-gitbook.vercel.app/url/gitbook.com/docs/create-content/content-structure/collection.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 `build a script that syncs our docs to a CMS` 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.
