> For the complete documentation index, see [llms.txt](https://uci.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uci.sunbird.org/use/developer.md).

# Developer - Contribute to UCI

I am an open-source enthusiast and I want to contribute to the Sunbird UCI

[**UCI Basics**](/use/developer/uci-basics.md)

As a new developer, before you contribute to UCI, you should get familiar with a few internal basics about UCI This section dives deep into the basics of UCI, setting you up for a good, contribution journey.

[**Development Environment**](/use/developer/development-environment.md)

This section helps any developer to get ready with the local setup of the codebase to start their contribution journey.

[**API Documentation**](/use/developer/api-documentation.md)

This section covers relevant APIs required for different use cases for any adopter in their journey of using UCI.

[**Database Schema**](/use/developer/database-schema.md)

This section provides essential information regarding the Database Schema necessary for various use cases, assisting any adopter throughout their UCI utilization journey.

[**Contribution Guide**](/use/developer/contribution-guide.md)

This section covers a long range of items, from the basics of how you contribute your first PR to how you contribute a new adapter and a new transformer.

***

***


---

# 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://uci.sunbird.org/use/developer.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.