> 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/~/revisions/hfepfFy5E9C1WpLCChmV/education-manual/how-to-create-a-workshop.md).

# How to create a workshop

### Intro

This guide is for you, if you want to create a new CorrelAid Event for the first time and don't know the steps involved yet or if you just want to check that you don't forget any steps in between.

The general phases in creating a CorrelAid event are the following:<br>

<figure><img src="https://2365861684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lvg_oIb4oZtCuInS01x-887967055%2Fuploads%2FrSwzipJpOIlMxdJvZ8Ta%2FEvent_anlegen.png?alt=media&amp;token=ed5b2805-91e3-4c84-a1a7-a1db339d9531" alt=""><figcaption></figcaption></figure>

### Tools

The tools used in the event creation are:&#x20;

* [Nextcloud Event deck](https://cloud.correlaid.org/apps/deck/board/67) for task tracking
* [GoogleDoc](https://docs.google.com/document/d/1uByPH0OqM_gj4E6CFbRjCJxWqVXCs-5jeEh6FZRWGa4/edit?usp=sharing) for saving the event description
* Canva for creating beautiful social media posts
* Zoom for creating the video call and invitation link (login info is saved in Bitwarden)
* [Pretix](https://pretix.eu/control) for participant management (they can register for the event and unregister from it and will receive an e-mail with the Zoom Link and a calendar invite, login info is saved in Bitwarden)
* [Kobo](https://kobo.correlaid.org/) for creating feedback forms

In the following sections you can find all the ToDos during each of the phases. These ToDos are also available in the event template card in the [Events Nextcloud Deck](https://cloud.correlaid.org/apps/deck/board/67).

An overview of all events and their descriptions can be found in this [Google Doc](https://docs.google.com/document/d/1uByPH0OqM_gj4E6CFbRjCJxWqVXCs-5jeEh6FZRWGa4/edit?usp=sharing)

### Planning

* Card created in deck & checklist copied&#x20;
* Clarification of&#x20;
  * Appointment&#x20;
  * Speaker&#x20;
  * Title&#x20;
  * Teaser&#x20;
  * Short description&#x20;
* Add that info to the GDoc [here](https://docs.google.com/document/d/1uByPH0OqM_gj4E6CFbRjCJxWqVXCs-5jeEh6FZRWGa4/edit?usp=sharing) such that we have an overview of all events
* (Create extra card on separate board if necessary: Create content for the event)
* Think about how to collect feedback for your event!&#x20;
  * Is there a [kobo form](https://kobo.correlaid.org/) that you can resuse?

**End result:** complete description of the event -> one document with all short descriptions [here](https://docs.google.com/document/d/1uByPH0OqM_gj4E6CFbRjCJxWqVXCs-5jeEh6FZRWGa4/edit?usp=sharing)

### Publication

* Create Zoom link (see [instructions](https://docs.google.com/document/d/1dBx4m3QBFhB50s89PWSqOALcr3A1dzdBBxltEkKqhE0/edit?usp=drive_link))&#x20;
* Create Pretix event (see [instructions](https://docs.google.com/document/d/1dBx4m3QBFhB50s89PWSqOALcr3A1dzdBBxltEkKqhE0/edit?usp=drive_link))
* Create an entry in the [PR Posting calendar](https://calendar.google.com/calendar/embed?src=c_omulbbbol3sv57go1l0nvfpng8%40group.calendar.google.com\&ctz=Europe%2FBerlin) (one week before the event)&#x20;
* Write **PR date as deadline** in the title of the card&#x20;
* Add event to [CorrelAid event calendar](https://www.correlaid.org/veranstaltungen/?viewType=list)
* Create an entry in public calendars:
  * [D64](https://kontakt.d-64.org/ticker/veranstaltungsliste-d64-ticker/)
  * [CDL Civic Data Cafe Calendar](mailto:undefined)
* (Tag person who is to advertise on card - we don't have that person yet so you are responsible for advertising)&#x20;

**End result:** Entry in the CorrelAid event calendar (and others)

### Advertising

* Create content&#x20;
  * Image: Templates can be found [here](https://www.canva.com/brand/brand-templates)
  * Text: Get creative.
  * Optional: Reel (Easily convert your image with the magic switch function in Canva)
* Post article&#x20;
  * [LinkedIn](https://www.linkedin.com/company/15245842)&#x20;
  * [Mastodon](https://masto.ai/@correlaid)&#x20;
  * [Instagram](https://www.instagram.com/correlaid/)&#x20;
  * Slack channels that apply

**End result**: Published posts on all social media channels

### During the Event &#x20;

* Document participants (screenshot)
* Share feedback link with participants

**End result**: successful workshop 🚀 , list of participants, materials

### Follow-up&#x20;

* Send materials and feedback link to participants (template in Education Mail)&#x20;
* For education events:&#x20;
  * Upload materials to [GDrive educational resources](https://drive.google.com/drive/folders/1Qg42zUvl7lhSKdRRM4l6CUyBS1BP5qbe?usp=drive_link) and change permissions to "everyone can view"
  * Add materials (non-editable) to ["Bildungsressourccen" in CMS ](https://cms.correlaid.org/admin/content/Workshops)
  * Fill out list of participants in [Nextcloud ](https://cloud.correlaid.org/apps/files/files/16073?dir=/03_education)
* (Forward feedback to external speakers)

**End result:** Number of participants and feedback are documented, materials are stored in a freely accessible and retrievable format\
\
And last but not least: have fun :tada:


---

# 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/~/revisions/hfepfFy5E9C1WpLCChmV/education-manual/how-to-create-a-workshop.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 `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.