> For the complete documentation index, see [llms.txt](https://docs.kodesage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kodesage.ai/key-features/automatic-documentation.md). # Docs Studio Documentation feature overview Kodesage generates and updates comprehensive documentation across the codebase, significantly improving onboarding times and easing transitions between vendors. As Kodesage is synced with the codebase, issues, wikis, and other sources in real time, documents will always be up to date as systems evolve. We will provide various documentation templates that you can choose from, to ensure that your systems are documented in a consistent format, and that they also meet the relevant legal requirements. Documents will include diagrams to improve explanations, and describe system dependencies. One the first draft is generated, data sources can be fine tuned on a section level within each sub chapter. **Getting started with Docs Studio** **Step 1:** Select the documentation template
Kodesage docs studio - template selection
**Step 2:** Select data sources
Kodesage docs studio - data source selection

Select data sources for document generation

**Step 3:** Create documentation After you have selected the data sources, you can click on "Create", and Kodesage will generate the documents for you according to the selected template **Step 4:** Review documentation Once the documentation has been generated, you will be able to select it from the list of documentations to review the content by clicking on the relevant documentation name.
Kodesage docs studio - editing existing documents

Select the relevant documentation from the list

Once you have selected the relevant document, you will be able to review, approve and modify the content.
Kodesage docs studio - editing and approving documents

Review documentation

--- # 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.kodesage.ai/key-features/automatic-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 `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.