Any designer on the team can contribute to the Orbit Figma UI Kit — whether you’re fixing a bug or adding new patterns and variants.
Keep Figma in sync with code
Components, features, or patterns shouldn’t be added to the Figma UI Kit unless they exist in Orbit’s coded components. Keeping Figma in sync with the codebase prevents confusion and keeps tooling consistent across resources.
Do
Add a Figma change only when there’s a matching coded component in Orbit.
Don’t
Introduce a Figma-only component or variant that has no counterpart in code.
How to contribute
- Open an issue (or assign yourself to an existing one), give it a descriptive title, add the “Figma UI Kit” label, and describe the change.
- Create a branch in the Orbit Components Figma library with a descriptive name — ideally referencing the issue number, e.g. “[4963] Navigation design changes”.
- Make the necessary changes in the new branch.
- Document all changes on the “Release notes” page within the UI kit.
- Add a design reviewer from the Orbit team to review the changes on your branch.
- Once reviewed and approved, an Orbit designer merges your changes into the main branch and publishes the update.