> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/about/contributing.md).

# Contributing

Open Collective is an open source project and we love to receive contributions from our community — you!

First, thank you for considering contributing to Open Collective! It's people like you that make this such a great community. We welcome any type of contribution, not only code.

Check out our [Roadmap](/help/product/roadmap.md) for the latest priorities.

You can help with: 

## **Quality Assurance**

File [bug reports](https://github.com/opencollective/opencollective/issues), the more details you can give the better

## **Internationalization**

Translate Open Collective's interface!

{% content-ref url="/pages/-Ls3oHlEQq1M9eMZrJ-G" %}
[Translation](/help/contributing/translation.md)
{% endcontent-ref %}

## **Documentation**

Suggest changes to this documentation!

{% content-ref url="/pages/-Ls3oHlB5mtSJNugEM4G" %}
[Documentation](/help/contributing/documentation.md)
{% endcontent-ref %}

## **Marketing**

If you would like to share something with the marketing team please join our [Discord](https://discord.opencollective.com) and post on the #news channel. 

Write blog posts and share success stories! We offer a $100 blog bounty to any Collective who wants to tell their story. Please [contact us](https://opencollective.com/contact) if you're interested.

## **Design**

Coming soon! 

## **Code**

There are always plenty of [open issues](https://github.com/OpenCollective/OpenCollective/issues)! We also have [Bounties](/help/contributing/development/bounties.md).

{% content-ref url="/pages/-Ls3oHksb1K6NSZxCOq5" %}
[Development](/help/contributing/development.md)
{% endcontent-ref %}

## **Feature ideas**

[Raise an issue](https://github.com/opencollective/opencollective/issues/) with your suggestion!

## **Peer Support**

Answer questions on our [Discord](https://discord.opencollective.com)! 

## Code Contributions

Unsure where to begin contributing to Open Collective? You can start by looking through the `good first issues`label, which should only require a few lines of code, and a test or two.

Want to get paid for contributing code? Check out our [bounty program](/help/contributing/development/bounties.md).

**General guidelines**

* The strings must be internationalized. See [/help/developers/translations](https://docs.opencollective.com/help/developers/translations)
* Whenever it's possible we must use `styled-components` to write styles. See [OC Styleguide](https://styleguide.opencollective.com/)
* Icons must be imported from the [styled-icons](http://styled-icons.js.org/) library.
* Tests written with Cypress must follow our [good practices](https://docs.opencollective.com/help/developers/testing-with-cypress) conventions.

### Code review process

The bigger the pull request, the longer it will take to review and merge. Try to break down large pull requests into smaller chunks. If it's a bug fix, it will probably be quickly merged and deployed. If it's a new feature, it will need more testing and review.


---

# 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.opencollective.com/help/about/contributing.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.