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 for the latest priorities.

You can help with:

Quality Assurance

File bug reports, the more details you can give the better

Internationalization

Translate Open Collective's interface!

Documentation

Suggest changes to this documentation!

Marketing

Write blog posts and share success stories! We offer a $100 blog bounty to any Collective who wants to tell their story. Just reach out to support@opencollective.com if you're interested.

Design

Help Collectives make a logo or a background image! Check out the Design Collective and how they work.

Code

There are always plenty of open issues! We also have Bounties.

Feature ideas

​Raise an issue with your suggestion!

Peer Support

Answer questions on our Slack!

Code Contributions

Unsure where to begin contributing to Open Collective? You can start by looking through the good first issueslabel, 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.

General guidelines

• The strings must be internationalized. See /help/developers/translations​

• Whenever it's possible we must use styled-components to write styles. See OC Styleguide​

• Icons must be imported from the styled-icons library.

• Tests written with Cypress must follow our good practices 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.