Active theme set to LightDarkLight high contrastDark high contrast and saved in preferences.
Copied to clipboard.
Error submitting your feedback! Please try again.


Nord’s contribution model allows product teams to add new features based on their product requirements. At the same time, it allows us to keep an eye on the quality and consistency of the user experience.

Our team follows a hybrid model where the central design system team is responsible for the overall direction. Growth is partly pushed to the consumers, who drive the evolution of Nord. This hybrid model helps us keep Nord accurate and actually useful.

How to get started #

When you start designing a new feature, you may come across a Design Token, Component, or Template that isn’t defined in the Nord Design System. When that happens, you should reach out to the Nord team to make a contribution.

You can either do that during our office hours or use a form that let’s you submit a contribution ticket. This ticket will help our team to understand what you’re trying to achieve, and what’s stopping you from achieving this with Nord today. The submitted contributions are grouped into three categories similar to the model Zalando uses:

  1. Light contribution: A small design tweak to an existing component or style.
  2. Medium contribution: A bigger change to an existing component or UX pattern.
  3. Heavy contribution: Creating a brand new component, UX pattern or tool.

In order to determine the contribution weight, please see the following diagram:

Nord Design System contribution process and different levels of contribution

Creating a ticket #

You can create a new contribution ticket here. All submitted tickets automatically sync to our issue tracker backlog. Our team meets every Monday morning to review bug reports and contribution tickets and to provide updates back to the product teams.

Submit ticket
You need to be logged in with a Nordhealth account to submit tickets.

Contribution process #

Our team follows the contribution process defined below. The process may vary depending on the level of contribution:

  1. Contribution proposal: The first step of a contribution is always a conversation. We want to reduce potential rework and frustration for the contributors by refining the solution before the work begins. Contribution proposals help our team to understand what you’re trying to achieve, and what’s stopping you from achieving this with Nord today.
  2. Kick-off: For medium and heavy contributions, we schedule a kick-off meeting with your team. During this meeting we agree on the scope of contribution, discuss your involvement, and also confirm timelines.
  3. Collaboration: We like to think about contribution as a way of collaboration. We’re here to support you and your team on this journey. We also aknowledge that the product team designers and developers are experts in their team domain, so we often have our people pair up with your team when designing for specific requirements.
  4. Review: Before publishing the new feature, we want to make sure that the contribution conforms to our high standards for accessibility, usability, and consistency in user experience.
  5. Publish: In the last step we make sure that the new feature is documented, communicated, and showcased within the company when it gets published.

Contribution tools #

To contribute, you need access to some or all of the following tools:

Nord Figma Project

Nord GitHub Repository

Our private repository, not for public use.

Nord Slack Channel

Practical guides #

Check out these practical guides to help you understand how to design for Nordhealth’s platforms using Nord Design System.

Backlog Prioritization Model

Nord Design Principles

Naming of Things

Accessibility Checklist

Color guidelines

Grid guidelines

Typography guidelines

Theming guidelines

Using Web Components

Frequently Asked Questions

Getting support #

Have a question about contributing? Please head over to the Support page for more guidelines and ways to contact us.

Was this page helpful?

Send feedback

We use this feedback to improve our documentation.

Edit page