> For the complete documentation index, see [llms.txt](https://docs.coreframework.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreframework.com/introduction/navigation-of-the-documentation.md). # 🔍 Navigation of the Documentation We are constantly trying to improve our documentation and our aim is to make it easy to follow, we hope that you have no issues with the navigation. Our documentation is structured to help you quickly find the information you need. It is divided into several sections, including Getting Started, Core Features, Integration Guides, and Troubleshooting. Each section is further subdivided into detailed topics that cover everything from basic setup to advanced customization options. Use the search function for direct queries, or navigate through the table of contents for a broader exploration. Links to video tutorials and downloadable resources are also available throughout, to enhance your learning experience. {% hint style="info" %} Have any advice or feedback on our documentation? Please let us know! {% 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.coreframework.com/introduction/navigation-of-the-documentation.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.