> For the complete documentation index, see [llms.txt](https://hub.fruitsalad.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.fruitsalad.ai/rooms/hackathon.md).

# Hackathon

The Hackathon Room is a virtual ecosystem meticulously designed for hosting hackathons remotely. It encompasses a variety of spaces:

* **Reception Area**: A welcoming space for participants to gather, network, and receive information about the event.
* **Team Discussion Spaces**: Equipped with interactive whiteboards and collaborative tools, these areas allow teams to brainstorm, code, and develop their projects in real time.
* **Presentation Rooms**: Specially designed for teams to showcase their projects, equipped with multimedia capabilities for effective demonstrations.
* **Group Discussion Halls**: Larger areas suitable for workshops, seminars, or general discussions among all participants.
* **Judges' Lounge**: A private, quiet space for judges to deliberate and evaluate submissions, away from the hustle of the main event.
* **Networking Zones**: Informal areas designed to encourage interaction and networking among participants, mentors, and judges.

This virtual venue replicates the dynamic and collaborative environment of a physical hackathon, ensuring an engaging and productive experience for all participants.


---

# 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://hub.fruitsalad.ai/rooms/hackathon.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.
