Contributors guide

Anchor is built using a inner-sourcing contribution model, which mean that Anchor gets contributions from within the Tryg organisation. This model allows any consumer to request and request changes to the library.

Back

Install the GitLab CLI

Some examples use the glab CLI package for creating issues and forking. To install that package, click here.

Contributing to Anchor

The contribution model is essential to expanding the component library. If you find any errors, missing documentation, or have suggestions for improvement, you are not only allowed but actively encouraged to contribute fixes.

How to Contribute

To make a contribution to Anchor, follow these steps.

Issues

If you find content that is obsolete, technically inaccurate, or unclear, start by creating an issue.

This is a great way to give specific feedback and ensure the technical content is up-to-date and technically accurate.

glab issue create

For creating an issue via the web, go here. click here.

Merge requests

To suggest more comprehensive changes or make updates yourself, feel free to make documentation changes by forking the repo and then submitting a merge request.

Fork the repo and clone it.

git clone https://gitlab.devops.prdroot.net/service/designops/ui-library.git

Create a new branch and make your changes.

git checkout -b my-branch

Commit your changes with a message with a brief summary message:

git commit -m "commit message"

Push up your branch:

git push origin my-branch

Commits and Merge Request Guidelines

MR titles should be descriptive enough for reviewers to understand what is being changed and have a description that explains why the change is being made.

For more detailed information about the format we expect for commits and merge requests, please refer to the Commits and Merge Request Guidelines. While the process is not daunting, we do require minimal oversight and structure to handle the load as usage of the Design System scales.

Written by

Alexander Wennerstrøm

At

Thu May 01 2025