> 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/readme.md).

# Welcome

Hi! Welcome to the CorrelAid docs. Here, we have collected information about how we work internally. All the content is continuously evolving and changing as we grow as an organization. We hope to document the status quo here but sometimes things might change.

This work is licensed under a [Creative Commons Attribution 4.0 International License](http://creativecommons.org/licenses/by/4.0/).

[![](https://i.creativecommons.org/l/by/4.0/88x31.png)](http://creativecommons.org/licenses/by/4.0/)

Read more about the license [here](https://github.com/CorrelAid/docs/blob/master/LICENSE.md).

## Wiki

How does CorrelAid *internally* work? Who do I need to talk to if I need xyz?

{% content-ref url="/pages/-LyYVwm-KCWTOkGf0n5A" %}
[How We work – Hitchhiker's Guide to CorrelAid](/wiki/hitchhikers-guide.md)
{% endcontent-ref %}

## CorrelAidX Manual

All about how local chapters work, how you can start your own, what you can do in a local chapter, different possible formats etc.

{% content-ref url="/pages/-LvgeeWMAtFsFxzqNont" %}
[What is CorrelAidX?](/community/what-is-correlaidx.md)
{% endcontent-ref %}

## Project Manual

A manual for coordinators and leads of CorrelAid projects. But might be interesting to everyone else as well! This is still a work-in-progress.

{% content-ref url="/pages/-M-oO8SzTGKMf73HjsiM" %}
[CorrelAid Data4Good projects](/projects/project-coordinators/data4good-projects.md)
{% endcontent-ref %}

If you cannot find the answer to your problem, do not hesitate to contact our [remote office team](mailto:info@correlaid.org) or ask your question in #help on Slack.


---

# 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.correlaid.org/readme.md?ask=<question>&goal=<user_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.