Carbon is free to use for anybody building a product or website, and the Carbon community is always working to make it better. Contributors like you help to make Carbon great, and so we’re glad you’re here.
Contributions are not limited to code. We also encourage feedback, documentation, new designs, and tools.
All you need is a public GitHub account to get started. Most contributions begin with a GitHub issue using one of these templates:
Carbon lives on GitHub. All work, discussion, issues, bugs, features, improvements, and comments happen right out in the open where everyone can see. As we mentioned, you’ll need a public GitHub account to contribute.
If you’re looking for something that we don’t have, or you notice something could be improved, you have two options:
Open an issue for the request. We’ll review the issue and get back to you with next steps. If we decide the request should be part of our pipeline, we’ll add it to our roadmap. There are never timeline guarantees for requests, but we’ll do our best to give you an estimate.
Begin the work yourself and contribute it back to Carbon. We appreciate complete contributions but also works in progress. You’re welcome to open an issue to surface your work and we’ll weigh in and help where we can.
Regardless of how you choose to contribute, we encourage you to open an issue as early as possible in the process.
If working with GitHub sounds like a lot, check out this free video series. It’s one of our favorite resources.
Users are members of the community who use Carbon guidelines, assets, and tooling. Anyone can be a user, and we encourage users to participate in the community as much as possible.
Contributors are members of the community who contribute to Carbon in a material way. Anyone can be a contributor. In addition to participating as a user, you can also contribute by:
Maintainers are members of the community who are committed to the success of individual Carbon projects. In addition to their participation as a contributor, maintainers:
Carbon Design System projects typically use a fork and pull request workflow for contributions. Specific instructions can be found in each project’s GitHub