Contributing to NerdWallet's shared design system enables:
- Pods to reuse and improve product work and worfklows
- Pods to increase velocity, product coherence, and product quality
- Nerds to increase their understanding of NerdWallet product architecture
There are many different ways (big and small) to contribute to Currency! We highlight a few popular questions below.
How do I propose a new design?
Mock up a design and share it with the designers working on Currency. We'll see if it can be added to the design system library as either a new design guideline rule, small change, or a completely new component.
How can I contribute a small bug fix to a Currency component?
That's great! Any engineer should feel empowered fix a bug through a pull request in the Currency GitHub repo . This lightweight contribution shouldn't require larger stakeholder alignment with Design and Product.
If you want to validate the fix before hand, feel free to reach out in the #currency Slack channel.
How do I get a new feature or larger contribution into Currency?
You can create a request on Aha :
- State the problem being solved.
- Audit the problem. Does the problem exist across more than two apps?
- Why don't existing components solve this problem?
The core Currency designers and the larger design team will review on a regular cadence and reach a conclusion about whether the given solution should be adopted or abandoned. If adopted, the work will ticketed, and prioritized based on standard Scrum processes NerdWallet teams follow.
Can I accelerate my feature request?
Yes! If your team has bandwidth to contribute the new feature, one way to ship new Currency updates faster is to lead the implementation yourself. Through the process, FEI and Currency Design can consult (design review, talking through functionality, etc). This is a good hack to leapfrog request from the back of the queue.