Ways to Contribute
Our community welcomes contributors with diverse skills:- Code Contributors - Developers who improve Celo’s protocol and infrastructure
- CIP Contributors - Authors of Celo Improvement Proposals
- Documentation Contributors - Writers who create and maintain technical documentation
General Contribution Guidelines
Whether you’re contributing code, documentation, or other content, these principles apply:- Fork the repository - Always work in your own fork before submitting changes
- Use PRs for changes - Pull requests are preferred, especially for small changes like typos
- Work in branches - Use feature branches, not master/main, for ongoing work
- Submit regularly - For non-trivial work, submit PRs regularly to get feedback
- Quality matters - Double-check your work before submission
- Be objective - Remain fact-based and neutral in tone
PR Best Practices
For effective contributions:- Create meaningful PRs with clear descriptions
- For works in progress, use “WIP” in the title
- Request appropriate reviewers (check CODEOWNERS when unsure)
- Explain dependencies and breaking changes
- Include relevant tests and documentation updates
Tutorial Contributions
Share your Celo experience through blog posts:- Create files in the blog directory using format
YYYY-MM-DD-post-name.md - Include proper front matter (title, description, author info)
- Use
<!--truncate-->to define post summaries - For images, create a folder with the same naming convention containing your post (as index.md) and assets
For questions or discussions, use the Celo Forum or Discord.