> 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/what-is-an-interest-group.md).

# What is an Interest Group?

An Interest Group (IG) is a structured, community-driven learning space where students with shared passions come together to build real skills and create substantial outcomes.

An IG exists to convert domain interest into structured skill development and tangible proof-of-work. It operates through:

* Structured learning roadmaps aligned with µLearn levels
* Regular knowledge sessions (office hours)
* Hands-on projects and challenges
* Mentorship from peers and industry experts
* Documented proof-of-work and portfolios

An Interest Group goes beyond informal discussion. While open conversations and idea exchange are encouraged within the community, each IG operates with structured roadmaps, defined milestones, and measurable outcomes to ensure meaningful progress.

→ To understand why IGs matter, go to [**\[Why IGs Matter\]**](/ig-playbook/why-igs-matter.md)

→ To start a new IG, go to [**\[Starting an Interest Group\]**](/ig-playbook/starting-an-interest-group.md)

→ To join an existing IG, go to [**\[Joining an Interest Group\]**](/ig-playbook/joining-an-interest-group.md)


---

# 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/what-is-an-interest-group.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.