Open Collective is an online funding platform for open and transparent communities. We provide the tools to raise money and share your finances in full transparency.
This is the place to find all help and documentation related to Open Collective. It's a work in progress, so please feel free to give us feedback.
To suggest changes, click the Github icon on any docs page and make a pull request. If you're not sure how to do that, see the step-by-step guide at the bottom of this page.
See links for more details. Each chapter heading in the docs has its own more specific FAQ.
An Open Collective is a place for communities to collect and disburse money transparently.
Open Collective is different. It's fully transparent (you can see where money comes from and where it goes), and designed for ongoing communities, not individual creators or one-off campaigns.
People can contribute from anywhere by credit card, with donations denominated in the currency of the Fiscal Host. Payouts work everywhere our payment providers, Stripe and Paypal, serve.
Yes! One main purpose of Open Collective is to provide unincorporated projects the legal and financial structures to provide people receipts and invoices.
You've come to the right place! These docs explain the whole platform in detail.
We are an open source project and run as an Open Collective ourselves. You can contribute money, code or translations. And we'd really love it if you started your own Collective and contributed by growing the community!
For more info about how you can contribute to Open Collective, check the contributing page.
First of all, thank you! We really appreciate it.
This is a guide for people who are not familiar with editing files through GitHub repositories. If you are, feel free to use your own workflow.
0) Make sure you have a GitHub account and you're logged in.
1) Go to the docs page you want to edit and click the Github icon.
2) Click the edit icon (pencil) on the Github page that you will be sent to.
3) Make the edits you want to suggest. The formatting uses markdown. Click 'preview' to check if it's looking how you intended.
4) When you're done making changes, scroll to the bottom and select "Create a new branch for this commit and start a pull request." Put in a short description and click "propose file change".
5) Click 'Create Pull Request' to send your proposed changes to the documentation admins, who will review and merge them if they are approved.
If you have any questions about contributing to our documentation, please reach out to firstname.lastname@example.org.