> For the complete documentation index, see [llms.txt](https://gitbook-open-v2-preview.gitbook.workers.dev/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-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/create-content/content-structure.md). # Content structure Learn how sites, sections, groups, and pages organize your GitBook content. Content in GitBook is organized around your docs sites. Your organization contains sites, and each site is made up of **sections** — the pages you write and edit live inside a section. Related sections can be organized into **groups** to shape your site's navigation. The structure you see while editing is the same structure your visitors see on your published site.

:globe:

Sites

Create a site to publish and organize your documentation.Site workspace

:layer-group:

Sections

Create sections to organize the content within your site.Sections

:folder:

Groups

Create groups to organize related sections in your site.Groups

:file-lines:

Pages

Create pages to split up and edit the content in your documentation.Pages
--- # 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-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/create-content/content-structure.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.