> 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/weekly-twitches.md).

# Weekly Twitches

#### **Purpose**

The **Weekly Twitches** page is the central hub for μLearn’s recurring community programs: **Office Hours**, **Salt Mango Tree**, and **Inspiration Station Radio**.\
Mentors use this space to explore, join, and review sessions that connect learners and mentors across different zones.

#### **Page Overview**

The page displays three tabs : **Office Hours**, **Salt Mango Tree**, and **Inspiration Station Radio,** each containing colourful cards for sessions. Every card shows the **status**, **date**, **title**, and **host or campus**, with filters for **status** and **zone** at the top.

#### **Features / Sections**

* **Tabs**
  * **Office Hours** – Mentor-led open sessions tied to Interest Groups.
  * **Salt Mango Tree** – Interactive community discussions.
  * **Inspiration Station Radio** – Creative and motivational broadcasts.
* **Filters**
  * **Status Filter** – Choose between *All statuses*, *Upcoming*, *Ongoing*, or *Completed*.
  * **Zone Filter** – Filter by *All zones*, *North*, *Central*, or *South*.
* **Search Bar** – Quickly find sessions by title or topic.
* **Session Cards** – Each card displays the session’s date, title, host, and current status.
* **Details Panel** – Clicking a card opens a right-side panel showing full details — topic, campus, zone, date, status, description, meeting link, and interest group tags.

#### **Available Actions**

* Browse sessions by program, zone, or status.
* Click a card to view full details.
* Join live sessions via the **Meeting Link** when available.
* Review completed sessions for insights and references.

#### **Step‑by‑Step Workflow**

1. Open **Weekly Twitches** from the sidebar.
2. Select a program tab (e.g., *Office Hours*).
3. Use filters to narrow down sessions by **status** or **zone**.
4. Click a session card to view details in the right panel.
5. For ongoing or upcoming sessions, use the **Meeting Link** to join.
6. For completed sessions, review the description and interest group tags to connect with related mentors or topics.

#### **Statuses and Their Meaning**

| **Status**    | **Meaning**                          |
| ------------- | ------------------------------------ |
| **Upcoming**  | Scheduled for a future date.         |
| **Ongoing**   | Currently live.                      |
| **Completed** | Finished and archived for reference. |

***

#### **Tips & Best Practices**

* Use **Office Hours** to engage directly with learners and Interest Groups.
* Filter by **zone** to discover sessions relevant to your region.
* Review **Completed** sessions to understand community trends and mentor engagement styles.
* Keep your Interest Group active by participating regularly in **Salt Mango Tree** and **Inspiration Station Radio**.

#### **Notes / Limitations**

* Session creation and management are handled by program coordinators and Interest Group Leads.
* Mentors primarily participate through attending and contributing to sessions.
* Some sessions may not have active streaming links until shortly before they begin.


---

# 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/weekly-twitches.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.