<commit_before>---
layout: markdown_page
title: "UX Designer Onboarding"
---

Awesome! You're about to become a GitLab UX Designer!
Make sure you've checked out our [handbook](/handbook) beforehand, so you get a feeling
of how we work at GitLab. Below you'll find everything you need to start designing.
If something is missing, add it (as goes with everything at GitLab)!

### On this page
{:.no_toc}

- TOC
{:toc}

## GitLab Instances

We have two main GitLab instances, as explained in the
[general onboarding](/handbook/general-onboarding#gitlab-instances).

## Getting started with designing for GitLab

To start designing, follow the instructions for the
[GitLab Design Kit](https://gitlab.com/gitlab-org/gitlab-design).

## Design tools

Every UX designer gets a license to [Pixelmator](http://www.pixelmator.com/mac/) and [Sketch](https://www.sketchapp.com/)

Previously we used [Antetype](http://www.antetype.com/) and have [switched](https://gitlab.com/gitlab-org/gitlab-ce/issues/19790) to Sketch.

Old Antetype design files are still be valuable. If necessary, see: [Converting antetype files for use with sketch](https://gitlab.com/gitlab-org/gitlab-ce/issues/19864)

When in need of different tools like CC Photoshop and/or CC Illustrator, request those by filing an issue on our [internal issue tracker](https://dev.gitlab.org/gitlab/organization/issues).

Other tools can include, but are not limited to: [Framer](https://framerjs.com/), [Origami by Facebook](https://facebook.github.io/origami/), [Principle for Mac](http://principleformac.com/), and HTML/CSS/JS prototyping.

## Issues

As design can be subjective, discussion can heat up. Always try to be [direct](/handbook/#directness), but [kind](/handbook/#kindness). Try to give your best reasoning for your choices and evaluate everyone's opinions. Come up with a solution instead of discussing endlessly. If you think additional perspective is needed, mention a fellow UX designer in the issue.

## Relevant links

- [Engineering Handbook](/handbook/engineering)
- [Engineering Workflow](/handbook/engineering/workflow)
- [Product Handbook](/handbook/product)<commit_msg>Fix capitalization in UX Designer Onboarding<commit_after>---
layout: markdown_page
title: "UX Designer Onboarding"
---

Awesome! You're about to become a GitLab UX Designer!
Make sure you've checked out our [handbook](/handbook) beforehand, so you get a feeling
of how we work at GitLab. Below you'll find everything you need to start designing.
If something is missing, add it (as goes with everything at GitLab)!

### On this page
{:.no_toc}

- TOC
{:toc}

## GitLab Instances

We have two main GitLab instances, as explained in the
[general onboarding](/handbook/general-onboarding#gitlab-instances).

## Getting started with designing for GitLab

To start designing, follow the instructions for the
[GitLab Design Kit](https://gitlab.com/gitlab-org/gitlab-design).

## Design tools

Every UX designer gets a license to [Pixelmator](http://www.pixelmator.com/mac/) and [Sketch](https://www.sketchapp.com/)

Previously we used [Antetype](http://www.antetype.com/) and have [switched](https://gitlab.com/gitlab-org/gitlab-ce/issues/19790) to Sketch.

Old Antetype design files are still be valuable. If necessary, see [Converting antetype files for use with sketch](https://gitlab.com/gitlab-org/gitlab-ce/issues/19864)

When in need of different tools like CC Photoshop and/or CC Illustrator, request those by filing an issue on our [internal issue tracker](https://dev.gitlab.org/gitlab/organization/issues).

Other tools can include, but are not limited to: [Framer](https://framerjs.com/), [Origami by Facebook](https://facebook.github.io/origami/), [Principle for Mac](http://principleformac.com/), and HTML/CSS/JS prototyping.

## Issues

As design can be subjective, discussion can heat up. Always try to be [direct](/handbook/#directness), but [kind](/handbook/#kindness). Try to give your best reasoning for your choices and evaluate everyone's opinions. Come up with a solution instead of discussing endlessly. If you think additional perspective is needed, mention a fellow UX Designer in the issue.

## Relevant links

- [Engineering Handbook](/handbook/engineering)
- [Engineering Workflow](/handbook/engineering/workflow)
- [Product Handbook](/handbook/product)
{'fraction_non_alphanumeric': 0.10892691951896392, 'fraction_numerical': 0.004625346901017576, 'mean_word_length': 4.828840970350404, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 14, 'lorem ipsum': 0, 'www.': 6, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1686607', 'n_tokens_mistral': 1337, 'n_tokens_neox': 1240, 'n_words': 476}