> 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/admin/how-to-create-a-workshop.md).
# How to: Workshops at CorrelAid
Step-by-step guide to having a workshop event at CorrelAid
**Legend**:
* 💚 To Do for Volunteers & Remote Office
* :office: To Do for Remote Office Only
### 1. Planning
* [ ] 💚 Clarification of
* Date
* Speaker
* Title
* Teaser (1-2 sentences)
* Short description (e.g. relevance, topic, and learning objectives)
* Picture of the speaker
* [ ] 💚 Think about how to collect feedback for your event! Is there a [kobo form](https://kobo.correlaid.org/) that you can reuse? (if you need an account, please contact )
* [ ] :office: Create cards in PM-tool (milestone for workshop itself as well as to do's for creating and reviewing materials)
* [ ] :office: Share Canva-Slide-template and (if necessary) Github-Repo with the speaker(s)
### 2. Publication
* [ ] 💚 [Create Pretix event](https://docs.correlaid.org/wiki/infrastructure/pretix) (if you need an account, please contact )
* [ ] 💚 Add event to [CorrelAid website event calendar](https://www.correlaid.org/veranstaltungen/?viewType=list) (if you need an account, please contact )
* [ ] :office: [Create Zoom link](https://docs.correlaid.org/wiki/infrastructure/zoom#creating-a-zoom-event)
* [ ] :office: Create an entry in public calendars (if workshop is not only targeted at the CorrelAid-Community):
* [D64](https://kontakt.d-64.org/ticker/veranstaltungsliste-d64-ticker/)
* [CDL Civic Data Cafe Calendar](mailto:undefined)
### 3. Advertising
* [ ] :green\_heart: Use the workflow in #pr-post-this-for-me to initiate the promotion of the event (e.g. newsletter, social media, etc.)
* [ ] :green\_heart: Post information in Slack
### 4. During the Event
* [ ] :green\_heart: Document participants (e.g. screenshot and check-in asap after the workshop in Pretix)
* [ ] :green\_heart: Share feedback link with participants
### 5. Follow-up
* [ ] :green\_heart:Send materials and feedback link to participants (either template in Education Mail or directly via Pretix)
* [ ] :green\_heart: Configure certificate of attendance in [Pretix](/wiki/infrastructure/pretix.md#certificates-of-attendance) (if relevant)
* [ ] :green\_heart: Forward feedback to speakers
* [ ] :office: Document number of participants and feedback in our [monitoring overview](https://docs.google.com/spreadsheets/d/17EuFJD0flqb1JKbsXo4PgCCs4JMYKiPEwwLIM8mSKhU/edit?usp=sharing)
---
# 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/admin/how-to-create-a-workshop.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.
