> 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/education/general.md).
# General
General information about CorrelAid Education.
Our organisation's purpose: **education**! 📚\
We firmly believe that knowledge should be shared so that everyone can benefit from the advantages of data-driven decision-making - regardless of age, level of education or professional background. That's why we offer numerous programmes for non-profits and volunteers.
👥 Who we are
In addition to our numerous volunteer tutors and workshop holders who are committed to educational purposes at CorrelAid, the Education team consists of a permanent full-time team. You can find an overview on our homepage under the Team tab.
📎 How we organise ourselves
We plan all workshops and courses via Slack. We exchange ideas there and also like to meet up in a huddle or via Zoom to talk in person. Our #education channel is the central place for all educational matters. In the #volunteering-oppurtunities channel, we often publish volunteer positions such as tutor activities. There are also separate planning channels for our courses.
☎️ How to reach us
Do you have questions, suggestions or your own ideas that you would like to contribute to CorrelAid's Education team? Then send us an email directly to or contact us via Slack in the #education channel.
---
# 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.correlaid.org/education/general.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.