> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/wiki/infrastructure/gitbook-for-documentation.md). # Gitbook for documentation [Gitbook](https://www.gitbook.com/) is originally a tool for developers to build documentation. We use it to write and and maintain documentation that is mostly static, i.e. does not change often, and does not need to be edited by many people. One example of a Gitbook is this page, our docs. It can be either edited through the Gitbook editor (accessible only to people invited to our Gitbook team) or by using [GitHub](https://github.com/CorrelAid/docs) where the files are stored. ## FAQ ### I want to contribute a small section or propose a small change to the docs. Please make a pull request to the [GitHub repository](https://github.com/CorrelAid/docs). ### I want to write a longer section. Please ask in #infrastructure for the signup link. Then you'll be able to join our Gitbook space and add your content using the Gitbook editor. ### I heard that the CorrelAidX Berlin chapter maintains their meeting minutes and projects on Gitbook. How can I read them? Please ask in #lc-berlin for the link that'll give you read or write access to the Berlin Gitbook team. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.correlaid.org/wiki/infrastructure/gitbook-for-documentation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.