> For the complete documentation index, see [llms.txt](https://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.com/docs/create-content/content-structure/all-content.md). # All content Browse, search, and manage content across all of your sites, and content that isn’t part of a site yet, from one screen In GitBook, your content lives in [sections](/docs/manage-your-site/site-structure/site-sections.md) that belong to a docs site. The **All content** screen gives you one place to see everything in your organization: content from every site, and content that isn’t part of a site yet. ### Open All content From your organization **Home**, click **Content** in the sidebar. ### Browse, filter, and search Each row shows the content’s name and when it was last updated. Click a row to open it. To narrow the list, click the **All sites** filter and choose a site. To find something by name, use the **Search content** field. ### Create content Click **Create content** to start new content from this screen. It’s best that content belongs to a parent site. Create new content inside a site whenever you can — it keeps your structure, permissions, and publishing in one place. See [Site structure](/docs/manage-your-site/site-structure.md) to learn how sections fit into a site. ### Content that isn’t part of a site If your organization used GitBook before our navigation remodel, some of your content may not belong to a site. It still appears in **All content**, and you can keep editing and collaborating on it here. To publish that content, add it to a site as a section. Learn more in [Site structure](/docs/manage-your-site/site-structure.md). --- # 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://gitbook.com/docs/create-content/content-structure/all-content.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.