> 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/start-here.md).

# Start Here

The internet gave everyone access to information.\
μLearn gives everyone access to opportunity.\
Same idea. Different infrastructure. Built for humans.

You're probably here because one of these sounds familiar:

* What am I supposed to be building toward?
* Why does none of what I'm doing feel real?
* How do I get access to people and opportunities that seem out of reach?
* Is there anyone out there who thinks the way I do?

You're not alone in asking these. And you're in the right place.

Here's what happens when you show up:

Pick something you're curious about.\
Do something real, build it, write it, design it, solve it.\
Your peers review it. If it's good, it counts.\
Everything that counts becomes part of who you are here.

That's it. No gatekeeping. No paywall. No minimum qualification.Everything you build here lives in one place, a permanent record that grows every time you do something real. One profile. Permanent. Yours.

[**Create your profile →**](https://mulearn.org/)

Already know what you're looking for?

* Company or partner → \[[Section 9 - Initiatives](/initiatives.md)]
* Campus lead → \[[Section 8 - Running μLearn](/campus-chapter-playbook.md)]
* Mentor or volunteer → \[[Section 5 - Roles](/roles-and-responsibilities.md)]
* Government or institution → \[Section 11 - Replication]


---

# 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/start-here.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.