# Hackathon Communication Platform

## **Communication Platform**

**Pick a communication platform and ensure your hackers join it**. Slack and Discord are two of the most popular. We recommend Discord for your event because of their free voice chat capabilities.

Before joining and once on the platform, make hackers know that their behavior and actions are still subject to MLH Code of Conduct, and to be respectful. ***Digital spaces can increase harassment as people are hidden behind a computer, so it is key to make sure your attendees know you still take this seriously.***

### **At a minimum include the following channels on your platform:**

* **Team-Formation:** Channel for hackers to form teams
* **Carpool-Search:** Channel for hackers to find a ride from other hackers
* **Ask-Organizers:** Channel for hackers to ask organizers any questions that come up throughout the event. 
* **Introductions:** Channel for hackers to introduce themselves. Have your team set the norm for this by introducing yourselves. 
* **Random:** Channel for anything that isn't hackathon related. 
* **Ask-Mentors:** Channel for hackers to connect with mentors when they need help on their projects. 
* **Mentors-Internal:** Channel for mentors to talk with each other and with organizers. 
* **Admin:** Channel for your organizing team. We recommend creating an admin voice channel as well! 

Here is an example from an event Discord!

* Note that there are 2 "sponsor" channels here so that sponsors have a dedicated space to talk about their api's or workshops. 

  <figure><img src="/files/n3gCARqIo2AiH2lVlFN2" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://guide.mlh.io/general-information/event-logistics/hackathon-communication-platform.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.