File structure
The Pajamas UI Kit is comprised of multiple Figma files that organize separate, but related concepts. Each publishes a library of styles and components that can be enabled in your design files.
- đź“™ Component library: The main file for design components that are used in Pajamas and in all other files. The library is published as "đź“™ Component library" and enabled for all team design files.
- Design tokens: Design token implementation in Figma. How can I use design tokens in Figma? Published as the "Design tokens" library and enabled for all team design files.
- Data Visualization: Components, styles, and charts used within GitLab. Published as the "Data Visualization" library.
- GitLab Product Icons: The main file for product iconography. The library is published as "GitLab Product Icons" and enabled for all team files.
- GitLab Product Illustrations: The main file for product illustration. Published as the "GitLab Product Illustrations" library.
- Annotations and utilities: Shared resources to annotate and present Figma artifacts. Published as the "Annotations and utilities" library.
- Patterns and Page Templates: Shared global resources that includes components and design assets owned by feature teams, maintained in a shared space due to their wide usage. The file also contains globally useful abstractions and combinations that promote a more consistent UI. Published as the "Patterns and Page Templates" library, although many assets are only available as "sticker sheets" to copy/paste.
In addition to the links above, some files are available from the GitLab Product Design community page and the project repository.
Fonts
The UI kit files make use of GitLab Sans, and GitLab Mono. Refer to the type fundamentals for more information. The fonts are enabled in Figma automatically for GitLab team members, and are available to download in this package.
Plugins
It may change in the future, but at the moment we don’t use plugins for critical actions or capabilities to avoid making any part of the design process reliant on plugin updates or functionality. Rather, we believe that each user should determine which plugins to use for their own workflow.
Last updated at: