Contributing a pattern

Thanks for your interest in contributing patterns! Since this is a general guideline, feel free to grow or shrink this process however you need.

1. Write a short spec and design your pattern(s). The pattern could potentially be something you’re already working on. Here are some examples of other specs people have written.
2. Review the spec with us, your crit pod(s), and the Design Systems Committee
3. If you have time or are already planning to do usability testing on your product feature, test the pattern with users (be sure to tap into the PD org to see if research exists already)
4. Add it to the Paste site for all to use and reference 🎉

Have feedback on the process? Add to our feedback doc.

We’re here to partner with you throughout the pattern process to ensure you’re building something that is systemized and accessible. We’ll also help you add to the docs site, refine design assets, and create coded examples.

You’ll create and research the doc/pattern/artifact and socialize it within your crit pods, committees, and peers. PDs have great insight into product-specific customer problems, which means if you’re a PD, you’re especially primed to contribute a new pattern or update an existing one.

Patterns are for you and your teammates, so it’s up to you what scope and type of contribution will have the most impact.

• Creating a full, net-new pattern

• Creating a variation of a pattern

• Documenting one part of a pattern

• Sharing research related to a pattern

• Refining an existing pattern based on new information

Check out our list of most requested patterns to see what's available. Have a new idea? Reach out to your peers and create a Github Discussion to see if there’s a need for something else.