> 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/ig-playbook/core-ig-activities.md).

# Core IG Activities

**TLDR:** The two core activities that drive every IG are Office Hours and Impact Projects. Office Hours are the heartbeat of the IG. Impact Projects are how members create real value.

### <mark style="color:$primary;">Office Hours</mark>

These sessions are the heartbeat of your IG, conducted weekly or biweekly for 60-90 minutes, focusing on structured topic deep-dives from basics to advanced. Each session begins with a quick Tech Bytes update and ends with announcing the next topic. The goal is to enable consistent learning, strengthen community engagement, and prepare members for upcoming challenges. All sessions should be recorded, shared via µLearn, and documented with attendance and topics.

### <mark style="color:$primary;">Impact Projects</mark>

Impact Projects are meaningful initiatives designed and executed to create real value for your Interest Group, your campus, or the wider µLearn community.

These are hands-on projects carried out over a period of time, where you build, solve, lead, or create something impactful. They focus on applying your skills to real problems, showcasing not just what you learn, but the tangible impact you create through consistent effort and execution.


---

# 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/ig-playbook/core-ig-activities.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.