> 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/educational-formats/daten-kommunizieren.md).
# Daten kommunizieren
Course Period 2025-2026
{% hint style="info" %}
:flag\_de: Language: German
:busts\_in\_silhouette: Target Group: Non-Profit Organizations
{% endhint %}
Data can tell stories... if you know how! In this course, non-profits learn how to create vivid visualizations and compelling data stories. This involves selecting appropriate chart types, designing graphics according to perception principles, and preparing information for different target groups.
Basic experience in working with data or initial exposure to impact management is helpful, but participants do not need any special prior knowledge of visualization; we will start together step by step using practical examples from civil society. Participants will benefit from exchanges with other course participants.
### **How does the course work?**
* Period: 6 weeks à 2-4 hours/week or 4 days as a block course
* Format: Integrated learning format with interactive learning platform
* Online live session with data science tutors
* Studying in learning tandems
* Individual consultation hours
### **Ressources**
* Website:
* Learning Platform:
---
# 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/educational-formats/daten-kommunizieren.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.