---
# System prepended metadata

title: Untitled

---

## Code of Contribution


* The Contributor[^1] introduces him-/herself to the FIS3 UI Community for sake of good collaboration 
* The Contributor has engaged with the FIS3 Architecture and any change conforms to the FIS3 Architecture
* Jira ticket for the Contribution to the Shared FIS3 UI Toolkit exists and is shared with the FIS3 UI Community[^2] – New Design are added to the FIS3 Design System
* Rational reason for the Contribution is given and documented1)
* The Contribution[^3] complies with the FIS3 UI Minimal Standard of Quality (FIS3 UI Definition of Done)
* The Contributor is accountable for any timely maintenance, refactoring or bug fix work for any Contribution in the go-live and stabilization phase

[^1]: The party that contributes to the Shared FIS3 UI Toolkit. This can be an independent developer or a product team.
[^2]: The group of people how jointly work on the Shared FIS3 UI Toolkit.
[^3]: Contribution to the Shared FIS3 UI Toolkit (abbr. Contribution) means any source code contribution to the Shared FIS3 UI Toolkit.

## Contributing Process
>NOTE: The section is currently under development. Some links may be temporarily broken.

1. **Creating a branch**
First of all, familiarize yourself with the [Git workflow]() we are using in this project. Then, to actually start the development process, [create a new branch]() with the [appropriate name]().
2. **Making changes**
Before making any changes to the code base, we suggest you to check our [coding guidelines](https://gitlab.hlag.altemista.cloud/fis3/commons-ui/commons-ui-frontend/-/blob/master/doc/coding-guidelines.md). In order to better understand the project structure you can check this [document](). We've also collected a bunch of other useful development-related information [here]().
3. **Covering with tests**
If you've implemented a new feature or fixed a bug, it's always a good idea to cover your work with tests. In [this document]() you can find some helpful information about different types of tests we use in our project, testing guidelines, practices, and so on.
4. **Merging**
At this point, it's time to introduce the world to the incredible work you've done. [Here]() we've covered the whole process from preparing a local branch and creating a merge request to merging your changes into the master branch.

Other useful information can be found in the `docs` [folder]().