> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/general/resources.md).

# Resources

Dive into interactive workshops, webinars and additional resources to start your journey with MOSIP.

Welcome to the MOSIP Resources Hub! Explore the wide range of resources available to help you get started with and deepen your understanding of MOSIP. This section provides everything you need to explore, build, and collaborate with MOSIP.

#### 🌍 Introduction to MOSIP and Its Use Cases. <a href="#introduction-to-mosip-and-its-use-cases" id="introduction-to-mosip-and-its-use-cases"></a>

In this section, we will explore the importance of digital identification, the challenges nations face without robust ID solutions, and the key differences between functional and foundational IDs.

MOSIP offers a scalable, secure, and inclusive identification system that helps governments establish efficient and flexible national ID frameworks. You'll discover MOSIP’s core offerings, innovative modules, and how it seamlessly integrates into real-world applications.

Please watch the video below to get started 🚀

{% embed url="<https://www.youtube.com/watch?ab_channel=MOSIP&index=1&list=PLJH-POb_55z9bYTJDkTGGc8pxiInWod8t&t=2s&v=QpZQ6ZWZ1Dk>" %}

### **Additional Resources** <a href="#additional-resources" id="additional-resources"></a>

#### **🛠️ Development Resources** <a href="#development-resources" id="development-resources"></a>

* **Source Code**: Access MOSIP's open-source codebase on [GitHub Repositories](https://github.com/mosip).
* **Containers**: Find prebuilt MOSIP containers in the [Docker Repository](https://hub.docker.com/u/mosipid)
* **Maven Repository**: Explore MOSIP artifacts on the [Nexus Repository](https://oss.sonatype.org/service/local/repositories/releases/content/io/mosip/).

#### **🎓 Learning and Training** <a href="#learning-and-training" id="learning-and-training"></a>

* **Training Programs**: Learn through detailed courses available at the [MOSIP Academy](https://academy.mosip.io/).
* **Learning Videos**: Watch tutorials, walkthroughs, and webinars on the [YouTube Channel](https://www.youtube.com/channel/UCxvEtyjmc3_KR45BOKMLJLA).

#### **🤝 Community and Collaboration** <a href="#community-and-collaboration" id="community-and-collaboration"></a>

* **Community Forum**: Engage with the MOSIP community, ask questions, and share insights on the [MOSIP Community on Discourse](https://community.mosip.io/).
* **Website**: Explore our official website for comprehensive information at [mosip.io](https://www.mosip.io/).
* **LinkedIn:** Connect with us on [LinkedIn](https://www.linkedin.com/company/mosip-project/posts/?feedView=all).


---

# 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.mosip.io/1.2.0/general/resources.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.