There are several ways you can contribute to and participate in Primer:
All contributions to Primer need to follow our code of conduct.
If at any time you get stuck or need help, head to #primer on Slack or start a discussion in github/primer with your question.
If you have a question, feedback or suggestion, you can start a new discussion (GitHub staff only), or have a look at existing ones.
Primer office hours are held once a week and anyone at GitHub can join, ask questions and participate in ongoing conversations. The office hours Zoom invite links are posted in Slack before the meeting starts.
If you'd like to propose a new Primer pattern, big or small, let's talk! The best way to get started, especially if your proposal is in its early stages, is to start a new discussion (GitHub staff only).
If you're more certain about what you need, please open a pattern request issue (GitHub staff only). We will get back to you after our weekly backlog triaging session.
Documentation is a core part of Primer, and, just as design and code, we’re always trying to make it better and more useful. If you notice something missing, a typo, or have an idea of how the docs can be improved, please start a new discussion, or submit a pull request with a fix (you can do this directly via the “Edit this page on GitHub” link on the footer of docs pages).
Read the Primer guidelines for writing documentation.
You can contribute to new patterns either by design, prototype and build proofs of concept, test in dotcom, or directly to our Primer open source repos.
From the Primer project board (GitHub staff only), you can grab anything from Unprioritized backlog and Up next — just reach out to us first in Slack or the issue itself.
If you spot something that doesn’t look right in our design, code or documentation, open an issue and we'll triage it accordingly.
When contributing to Primer open source repos, please follow the repo's contributing guidelines: