> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/how-to-use-the-platform/general-pages/events.md).

# Events

#### Purpose

The **Events** module helps mentors discover community events, browse upcoming and past events, filter events by role and type, and view detailed event information.

#### Page Overview

The Events page features a highlighted event carousel followed by a searchable list of event cards. Mentors can filter events by community role and event type, then open any event to view its complete details.

#### Features/Sections

**Featured Events**

The top section displays featured events in a carousel.

Each featured event includes:

* Event title
* Event date
* Venue
* Event image
* Previous and Next navigation buttons
* Carousel indicators
* **I'm Going** button showing the number of attendees

**Search and Filters**

Use the available controls to narrow the displayed events.

* **Search events** — search events by name.
* **Role Filter** — filter events based on community roles:
  * All
  * Maker
  * Coder
  * Manager
  * Creative
* **Event Type Filter** — filter events by category, including:
  * Hackathon
  * Workshop
  * Webinar
  * Seminar
  * Bootcamp
  * Meetup
  * Conference
  * Competition
  * Ideathon
  * Cultural Event
  * Sports Event
  * Community Event
  * Expo
  * Networking Event
  * Tech Talk

**Event Cards**

Each event card displays:

* Event category
* Community role tag (if available)
* Event date
* Event title
* Organizer
* Venue
* Event status

**Event Details**

Selecting an event opens its detailed page containing:

* Event banner
* Event date
* Event time
* Venue or location
* Event mode (Online/Offline)
* Event visibility (such as Global)
* Event description
* Registration status
* **I'm Going** button with attendee count
* Organizer information

#### Available Actions

* Browse featured events.
* Search events by name.
* Filter events by role.
* Filter events by event type.
* Open an event to view its details.
* Mark your attendance using the **I'm Going** button.

#### Step-by-Step Workflow

1. Open **Events** from the sidebar.
2. Browse the featured events or scroll through the event list.
3. Use the search box or filters to find relevant events.
4. Select an event card to open its detailed page.
5. Review the event schedule, venue, mode, and description.
6. Check the registration status.
7. Select **I'm Going** if you plan to attend.

#### Statuses and Their Meaning

| Status              | Description                                             |
| ------------------- | ------------------------------------------------------- |
| Event Ended         | The event has already concluded.                        |
| Registration Closed | Registration is no longer available for the event.      |
| Online              | The event is conducted online.                          |
| Global              | The event is open to participants across the community. |

#### Notes

* The featured event carousel allows navigation between highlighted events.
* Search and filter options update the displayed event cards.
* Event cards open a dedicated event details page.
* The **I'm Going** button displays the number of users who have marked their attendance.
* Registration availability depends on the event's current status.


---

# 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.mulearn.org/how-to-use-the-platform/general-pages/events.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.