Contact us
How to get help from the Atlassian Design System team and contribute to the system.Check our guidance first
Before you reach out, look for an answer in these places.Get started
Start designing and developing beautiful interfaces with Atlassian Design System foundations, components, and standards.Foundations
Foundations create engaging user experiences. These include our tokens, guidelines, and visual styles: color, spacing, typography, and more.Components
Components are reusable building blocks that meet specific interaction needs. They combine to create intuitive user experiences.Tokens
Design tokens are the single source of truth to name and store decisions about the user interface, such as colors, typography, and spacing.Ask a question or book a critique
Visit developer community (public only)
Search the Atlassian Developer Community forum and post questions.Slack a question (Atlassians only)
Reach out to our team in the #help-design-system channel.Book a design critique (Atlassians only)
Request a crit session to get feedback on your designs.Empowering you to ship value to your customers is a priority. To avoid being a bottleneck, we'd love to be involved early in your app implementation through our participation channels.
If you need to add something or believe something is missing, post a question in slack so that we can offer support and connections.
Contribute a small fix or enhancement (Atlassians only)
A design system is never complete. It depends on contributions from Atlassian teams, so we’d love your help!
Atlassians can contribute by posting in our slack channel:
#help-design-systemIf you don’t work for Atlassian and have some feedback, let us know in the feedback collector available on each page of the site.
We are currently accepting contributions through:
- Fixes, such as removing bugs in the code, errors in Figma library components, and editing confusing documentation.
- Small enhancements, such as adding a new icon to the existing icon library.
These changes don’t break existing behavior and can be confined to minimize impact across the design system.
We can’t accept large contributions right now
Considering a design system component or pattern takes time. We have to think about every product and its use case, multiple brands, API design, and guidelines that apply to everyone.
At this time, we are unable to take these types of contributions:
- Major enhancements, such as adding a new feature to a component, or altering a property like a timeout on a flag.
- New components or patterns, such as data visualization.
These changes require system-wide coordination and impact code, design, and documentation.