The key goals are to create flexible, robust, and useful patterns that advance Primer's incremental innovation, while building upon an existing set of solid foundations.
Primer is built on strong foundations that should remain stable. Become familiar with guidelines on typography, color, spacing, and layout.
It's important to know what's coming into Primer, to avoid duplicated efforts and to accommodate upcoming changes to elements that may interact with what you're planning to work on.
Check what is currently being designed and built, as this may introduce new concepts and variations to existing patterns.
➡️ Primer backlog (GitHub staff only)
Before you start to create mockups and think of solutions, it's good to always carry out an audit of where similar patterns are used in github.com, and where it can potentially be used once a new pattern exists. You can also audit different products to see how they've solved similar problems.
Think about as many different use cases where the pattern can be used across github.com as possible. The goal is to create patterns that are flexible, but that solve concrete problems.
Finally, consider where a pattern will live in the context of the larger product. Don't design a single pattern in isolation of its possible surroundings.
@todo Coming soon!
The work that you're doing shouldn't be a surprise that you only reaveal when you're done.
Systems designers can provide extra context and considerations that are helpful to create a solid design.
Product designers can consider the designs in the context of their own product area and whether their specific use cases could benefit from your proposal.
Engineers can consider how something may be implemented, what is realistic within the existing constraints, and what is unfeasible.
There are different ways you can ask for and get feedback:
All Primer design patterns should take into account the following areas: