` elements to render collapsible menu items. This might not be a valid use-case for those elements, let's consider dropping them in favor of simple `v-if`s in the Vue components.
-
-## Implementation plan
-
-- [x] Drop the use of summary elements in favor uls and v-ifs.
-- [x] Do not automatically select the first child item when clicking on a parent.
-- [x] Keep the behavior where only one menu section can be expanded at a time.
-- [x] Improve navbar's accessibility by leveraing `role` and `aria-` attributes.",2
-86539036,2021-05-05 16:47:04.114,Adjust navigation items under Data Visualization,"Here is the current nav under data visualization in Pajamas:
-
-
-
-From discussion on https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2361#note_568114665, it sounds like the order of pages is because the nav items are automatically placed in alphabetical order. In this section, that leaves us with a surprising result - the Overview item is third and the more detailed pages (Charts, Color) are first.
-
-Should we consider re-ordering the pages in this section based on content rather than alphabetizing?
-
-If so, perhaps the order could be:
-
-- Overview
-- Color
-- Charts
-- Single stat",1
-86503119,2021-05-05 09:18:26.731,Document a conceptual object model for Jobs,"## Problem
-
-Jobs are the main building block of a pipeline. Understanding the essence of Jobs and the concepts associated with them can help us create a better experience around Jobs in GitLab UI. Currently, Jobs are not documented as an object in GitLab. It's difficult to find information around all the concepts associated with jobs and how they're represented in the UI.
-
-## Proposal
-
-Document Jobs using the Conceptual Object Model.
-
-This model allows for proper separation of concerns: concepts (meaning) and user interface (representation). In other words, a conceptual model is only focused on the concepts and how they relate to each other, not how it’s technically implemented or used in the UI. A conceptual model defines the objects and actions, and enumerates the attributes for every object. The language of the conceptual model diagram is meant to be as simple and accessible as possible to everyone, even if they are not familiar with these kinds of diagrams (for more information, see [Object Modeling for Designers](https://medium.com/@hpadkisson/object-modeling-for-designers-an-introduction-7871bdcf8baf).
-
-Here's an example of how we document the [Merge Request as an object in GitLab.](https://design.gitlab.com/objects/merge-request)
-
-#### Next steps
-
-- [x] Document the concepts associated with Jobs
-- [x] Map the concepts associated with Jobs
-- [x] Document the layouts for the representations of Jobs in GitLab
-- [x] Review the Figma file
-- [x] Merge to the Conceptual object model file in Figma
-- [x] Map the primary Job page layout
-- [x] Merge the semantic layout to the Layouts file
-- [x] Work on a documentation MR ([MR in review](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2713))
-
-## Working Figma files
-
-* [Job object model](https://www.figma.com/file/J68bePHXIN5OPWqaFFY9ri/branch/bMpqqGQtDoPqty4sAFPUsy/Conceptual-model?node-id=5423%3A453)
-* [Job semantic layout](https://www.figma.com/file/shVF8UZwrQtkNfMDjcrsyH/branch/PZruVNvWVcpdNwm69cXgeJ/Semantic-layouts?node-id=4636%3A208)",3
-86477742,2021-05-04 20:35:08.417,Themes > Adding missing color palettes,"Within Pajamas, Figma, and GitLab-UI we define a series of color palettes for each of our available themes. However, we are missing all of the options that are currently available in the product:
-
-
-
-Ensure there is continuity between the options in the product and the palettes in Pajamas.",2
-86245699,2021-04-29 20:09:27.201,A11y action > Increase input placeholder contrast,"## Purpose
-
-Placeholder text within a text input should have sufficient contrast (at least a 4.5:1 ratio).
-
-
-
-## Solution
-
-Use `$gray-500` for `placeholder` text.
-
-This should be updated both in Figma and GitLab UI.
-
-Source: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1475#note_550956831",1
-86201104,2021-04-29 09:11:31.477,add description to Toggle like input field,"### Problem
-
-I have a need to use a long description to explain what does this toggle is about instead of short help text like ""disabled by admin"". If I use the help text, it looks like this:
-
-Those live example copies need to be refined. But the length and format illustrate the problem we will face. Long copy and copy with ""learn more"". I think we should discuss this because in English the copy might be short, but in another language, a two-line description might be common when we face German or another lengthy language.
-
-| Live Example | Component |
-| --- | --- |
-| | |
-
-**This has two problems:**
-
-1. The description is far from the label it belongs to and closer to the label of the next item. This creates more cognition load for a user to figure out, this description belongs to which one?
-1. It is too long and visually looks unbalanced
-
-### Solution
-
-| vertical1 - Live Example | vertical1 - Component |
-| --- | --- |
-|  |  |
-
-Other explorations
-
-| vertical2 - Live Example | vertical2 - Component |
-| --- | --- |
-|||
-
-| horizontal Live Example | horizontal - component |
-| ------------ | --------- |
-|   |  |
-| | |
-
-
-
-
-cc: @gitlab-com/gitlab-ux/designers",3
-86162773,2021-04-28 18:54:54.496,A11y action > Update audit issues to include severity rating,"# Proposal
-
-We have a number of [accessibility audit issues](https://gitlab.com/groups/gitlab-org/-/epics/5387) open. We should include a severity rating for each finding.
-
-# Background
-
-> One thing I haven’t included in the audits I’ve done so far is the level of severity. I’ll try to do that from now on.
->
-> This is the same I’ve used before:
->
-> - **Critical:** prevents some or all users from performing critical tasks with no workaround.
-> - **High:** prevents some users from performing critical tasks, or where a workaround may exist.
-> - **Medium:** prevents some users from performing non-critical tasks, or where the user experience is seriously degraded for users with certain assistive technologies.
-> - **Low:** the user experience is degraded for users with certain disabilities or using certain assistive technologies.
->
->This is the rating Deque proposes:
->
->- **Critical:** This issue results in blocked content for individuals with disabilities. Until a solution is implemented content will be completely inaccessible, making the organization highly vulnerable to legal action.
->- **Serious:** This issue results in serious barriers for individuals with disabilities. Until a solution is implemented, some content will be inaccessible, or significant a work-around is required, making the organization vulnerable to legal action. Users with disabilities may experience significant frustration when attempting to access content.
->- **Moderate:** This issue results in some barriers for individuals with disabilities but would not prevent them from accessing fundamental elements or content. Users with disabilities may experience moderate frustration when encountering this issue.
->- **Minor:** This is an issue that may inconvenience a user but would not cause significant frustration in accessing content or accomplishing tasks.
-
-Source:
-https://gitlab.com/gitlab-org/gitlab-design/-/issues/1473#note_545158557, https://gitlab.com/gitlab-org/gitlab-design/-/issues/1473#note_545159441
-
-~accessibility ~""Category:FE/UX Foundations""",1
-86162768,2021-04-28 18:54:53.881,A11y action > Add content to Forms > Placeholders,"# Proposal
-
-Add documentation to ` Forms > Placeholders` that describes the following:
-
-> the intended use of placeholder text is for extra, non-essential information
-
-# Background
-
->the intended use of placeholder text is for extra, non-essential information.
->
->>I like this little nugget and I think it’d be worth adding something similar in an update to https://design.gitlab.com/components/form#placeholders.
-
-Source: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1470#note_538076572
-
-~accessibility ~""Category:FE/UX Foundations""",1
-86162754,2021-04-28 18:54:51.567,A11y action > Inclusive design presentation,"# Proposal
-
-Create a presentation that addresses inclusive design and showcase it to the UX Department in order to increase awareness of biases.
-
-@jeldergl is currently working on a presentation that would be a good fit to satisfy this.
-
-# Background
-
->Some training on how to recognize bias in design would be helpful. In other words, evaluating design against our own bias and examine if we’re meeting the needs of more than just those like us — whatever that us may be.
-
-Source: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1463#note_499957432
-
-~accessibility ~""Category:FE/UX Foundations",4
-85846218,2021-04-23 20:42:01.871,Dig into whether or not the status table is accurate,"As per discussion with Taurie: There is some concern that the [component status table](https://design.gitlab.com/components/status) isn't totally up-to-date.
-
-The goal for this issue would be to go through the [existing status table](https://design.gitlab.com/components/status) and dig into the `in progress` items to see if they can actually be moved to complete.",3
-85755120,2021-04-22 15:10:38.328,Extend guidelines on labels,"Discussion
----
-
-[Labels](https://docs.gitlab.com/ee/user/project/labels.html) in GitLab have historically been tightly coupled with Issues, Epics, and Merge Requests ~""group::project management"". There are other use cases (Compliance Frameworks or Topics) in GitLab where users are creating elements to categorize objects that would benefit from using [label](https://gitlab-org.gitlab.io/gitlab-ui/?path=/story/base-label--default) the component.
-
-> Scoped labels are a sub-type of labels, and their usage is determined by the user. A scoped label is differentiated from a regular label by the contrasting colors on the left and right sides of the label. - [Pajamas](https://design.gitlab.com/components/label/#usage)
-
-Pajamas merely states that there is only a differentiation in the UI, but there is a unique feature tied to [exclusivity](https://docs.gitlab.com/ee/user/project/labels.html#scoped-labels) in scoped labels for project management. Compliance Frameworks are currently using scoped labels just for visual flair, although it is not possible to apply more than one Compliance Framework to a project today.
-
-When considering the `scoped label` attribute, should this UI element always have exclusivity as a corresponding feature?",1
-85687189,2021-04-21 17:40:35.935,Brand > Combine brand basic and resources,"In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2345, `@ameliabauerly` mentioned that we could combine the Brand basics and Resources content into one page. We could add those links to the bottom of the Brand > Basics page and not need an entirely separate page for them.",1
-85687107,2021-04-21 17:38:54.431,Brand personality / Design principles table,"In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2345, we are removing outdated brand pages that are no longer shown in the sidebar. This includes the following table:
-
-
-
-Should we include this somewhere within our brand docs or possibly use it to better define our design principles?",2
-85592955,2021-04-20 19:58:52.988,Collapse sidebar after navigation on mobile devices,"The following discussion from !2301 should be addressed:
-
-- [ ] @oregand started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2301#note_556227195): (+3 comments)
-
- > @pgascouvaillancourt
- >
- > Great work on this, it looks super and feels great to use! I have left a selection of comments for you to check at your own time but your overall approach looks good to me here given the constraints you're working against with the keys && file boostrapping :smile:
- >
- > I was going to ask if we had supporting specs but see we don't have them in this repo yet :joy:
- >
- > One ~UX suggestion, we might want to auto close the sidebar on navigation from the search when we're on mobile but that's a non-blocking suggestion!
- >
- >
- > 
-
----
-
-On mobile devices, the navigation sidebar can be expanded and overlaps the primary content. From there, clicking any link properly triggers navigation through `vue-router`, but the sidebar remains expanded, hiding the content that's being accessed.
-
-Let's improve the ~UX by automatically collapsing the sidebar whenever navigation occurs.",2
-85279391,2021-04-15 23:56:05.764,Figma component > Table (updates to sorting and additional states),"
-
-## Description
-
-
-
-This is a follow up issue to [Figma component > Add Tables](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/721). The table currently is still missing responsive states and is not leveraging some of Figma's newer layout features.
-
-### Summary of overall table updates:
-
-- All cell content is now `top` aligned by default
-- The sorting arrow has been moved closer to the right of the header label, in order to make it clear which header label they belong to
-- On hover and on focus states have been to header cells if the configuration is set to sortable
-- A new 'compressed` table option has been added (https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/449)
-- A new row state has been added (https://gitlab.com/gitlab-org/gitlab-ui/-/issues/884)
-- A new `` component has been added (https://gitlab.com/gitlab-org/gitlab-ui/-/issues/1726)
-- A top border has been added to the header row in order to better visual understand where the table starts and ends on a page
-
-### Summary of Figma specific updates:
-
-Since the first version of the Figma Table component that has been added to our component library, Figma has introduced many new features specific to [Auto Layout](https://help.figma.com/hc/en-us/articles/360040451373-Create-dynamic-designs-with-auto-layout) that make creating tables more flexible. This update will make it easier for designers to create responsive tables in Figma that are easier to customize and lower the need to detach from parent components.
-
-**Sorting interaction spec:**
-
-
-
-### Rationale for current updates
-
-| Overall component usage (last 90 days) | Variants being used (last 90 days) |
-| ------ | ------ |
-|  |  |
-| **Insights:**
In the first version of the table component a lot of time was put into creating the multi-line variant which shows no usage. | **Insights:**
The checkbox variant is the second most used. This newer update makes it easier to turn on/off the selectable state for entire rows. |
-
-Note: Thank you @jeldergl for pulling these metrics from Figma.
-
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/Wli6qiEaC8rnXfeQiukJHw/Component-library?node-id=425%3A11)
-
-### References
-- https://getbootstrap.com/docs/5.0/content/tables/
-- https://mdbootstrap.com/docs/b4/jquery/tables/sort/
-- https://material.angular.io/components/table/overview#sorting
-- https://material.io/components/data-tables#anatomy
-
-### Demo walkthrough
-
-- :tv: https://youtu.be/7tEa-qT_MfY
----
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [x] **Assignee**: If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, please consider [transfering ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] **Assignee**: When applicable, [create an MR in this repository][new-gitlab-ui-mr] and apply the ""component-guideline"" template
- to create or update the component’s documentation page. If you do not have capacity, [create an issue in this repository using the ""Component documentation"" issue template][pajamas-component-documentation-template]. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: When applicable, [create an issue in GitLab UI using the ""Component"" issue template][gitlab-ui-component-template] to build or update the component code. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[pajamas-component-documentation-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-[new-gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new",2
-84821078,2021-04-07 20:17:15.813,FY22-Q2 Foundations KR2: Create a maintained backlog of Pajamas issues that enables product designers and engineers to easily find issues and contribute => 79%,"[FY22-Q2 UX Department: Foundations SubTeam OKR](https://gitlab.com/groups/gitlab-org/-/epics/5726)
-
-Objective: Ensure Engineering is able to iteratively contribute to and utilize Pajamas for stage work deliverables
-
-**KR2: Create a maintained backlog of Pajamas issues that enables product designers and engineers to easily find issues and contribute**
-
-- [x] Ensure all issues within the Pajamas repo have a workflow label. See our [workflow label board](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/boards/1835632) 336/336 => 100%
-- [ ] Ensure all issues within the Pajamas repo have a weight. See [issues without weights](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues?scope=all&state=opened&weight=None) 197/336 => 18%
-
-533/672 => 79%",13
-82133985,2021-04-01 16:22:35.504,Figma > Form > Add form_input_group,"
-
-### Description
-
-`form_input_group` was introduced in GitLab UI (https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/2115) which includes a form input that is grouped together with another element, such as a label or button.
-
-This component is being used on the `new fork` page, see https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53544
-
-We don't currently have this component within our UI Kit and the styling in GitLab UI does not match our visual language.
-
-The purpose of this issue is to get the component within Figma, and then to open up the needed issues in GitLab UI to correct the styling.
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/cdUPbjyDRc326Rk6KGyxKw/Component-library) (Branch is archived after merge)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: ~~Ask a [FE/UX Foundations designer][foundations-team]~~ Assigned to Figma trainee
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [x] **Assignee**: Move your working file to the shared Figma project:
- 1. [x] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [x] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",3
-81860969,2021-03-29 16:11:53.212,Include GitLab UI utilities,"The following discussion from !2300 should be addressed:
-
-- [ ] @markrian started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2300#note_540028499): (+2 comments)
-
- > **question (non-blocking)**: A quick grep suggests we don't use GitLab UI's utility classes in this repo. Should we?",1
-81418386,2021-03-22 14:45:44.188,Badge > Linked badges > Make examples in Pajamas the SSoT,"## Problem
-
-Embedded badge examples in Pajamas are different from GitLab UI. Having a SSoT will help accurately complete the badge accessibility audit https://gitlab.com/groups/gitlab-org/-/epics/5664.
-
-| **Pajamas** | **GitLab UI** |
-| ------ | ------ |
-|  |  |
-
-## Solution
-
-Ensure badge examples align with the [badge design specs](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=425%3A3) and that action badges dont underline text on hover.",2
-81248852,2021-03-19 03:53:26.938,Update guidelines around left menu items,"
-- [x] Guidelines around what the menu items in the left sidebar
- - https://design.gitlab.com/regions/navigation#contextual-navigation
- - What should be a primary level item vs secondary
- - Updated: https://design.gitlab.com/regions/navigation#left-sidebar
- - ⛔️ Should ""Labels"" be allowed to jump between a submenu item to parent level? https://gitlab.com/gitlab-org/gitlab/-/issues/21147#note_525491995
- - We are putting Labels into `Project information` https://gitlab.com/gitlab-org/gitlab/-/issues/329905
-- [x] Landing pages should be the first sub menu item
- - https://design.gitlab.com/regions/navigation#product-landing-pages
-
-
-## Draft outline
-
-### Parent item
-
-### Submenu items
-
-- Items in the submenu should help support navigation to the parent JTBD and supporting JTBD
-- High level features of the category",3
-81245967,2021-03-19 03:15:30.567,Update documentation for global navigation,"## Proposal
-
-Relates to this page https://design.gitlab.com/regions/navigation#global-navigation
-
-- [ ] Update documentation for the consolidated projects/group/more menu
-- [ ] Add example of the menus mentioned
-
-~""Category:Navigation & Settings""",2
-80557737,2021-03-09 13:55:08.340,Update the dropdown component with variants and add missing variants,"
-
-### Description
-
-
-
-@lvanc and I noticed that there are some cases are missing in our current dropdown component while adding the filter component. https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/720
-
-We can add this to the existing component as variants or/and instances.
-
-And switch to the variants style structure and make the component more flexible.
-
-| Icon + Text | Text + Help text | User profile |
-| ------ | ------ | ------ |
-| |  |  |
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/2OhkWPJsIE6FSbaTugAVPw/Component-library?node-id=425%3A14)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [ ] **Maintainer**: Review and approve assignee’s changes.
-1. [ ] **Maintainer**: Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [ ] **Assignee**: Move your working file to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [ ] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",2
-80543959,2021-03-09 10:32:29.713,Update segmented control visual style,"
-
-### Description
-
-create consistent button styles
-
-| Before | New |
-| ------ | --- |
-|  |  |
-
-
-#### Visual Design Changes
-
-- Selected states: remove shadows, used a border to indicate selection
-- Hover status: a light grey background $gray-50
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/7FLQ3LnDhj3vI7QnGAkTjn/Component-library)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [-] **Assignee**: Move your working file to the shared Figma project: (File automatically archived since it was a branch.)
- 1. [-] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [-] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [-] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [x] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",3
-80101565,2021-03-02 15:01:16.599,Update Figma text input to use variants,"
-
-### Description
-
-
-
-Figma introduce variants, it is time to update the text input field
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/OU6DPkNlneFHnXwcUILWfl/WIP-Update-input-text-field?node-id=1%3A2)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [x] **Assignee**: Move your working file to the shared Figma project:
- 1. [x] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [x] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [x] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [-] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [-] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",4
-79233372,2021-02-17 03:19:08.833,Document tree updates in Pajamas [Tree🌲],"Document any changes to the tree component here to be merged into [Pajamas](https://design.gitlab.com/product-foundations/interaction#drag-and-drop}https://design.gitlab.com/components/tree).
-
-#### 📌 Merge requests
-
-* ....
-
-#### ✨ Overall change highlights
-
-* ...",3
-86894837,2021-02-12 17:07:47.583,Introduce search to Pajamas,"As part of our [Pajamas engagement survey](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1394), we heard that people would like to be able to search through Pajamas to find exactly the information they need.
-
-How do we go about introducing search to Pajamas?",3
-78823017,2021-02-10 15:30:54.588,Document drag and drop updates in Pajamas [Drag & drop🤏],"Document any changes to drag & drop here to be merged into [Pajamas](https://design.gitlab.com/product-foundations/interaction#drag-and-drop).
-
-#### :pushpin: Merge requests
-- https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/1941
-- ....
-
-#### :sparkles: Overall change highlights
-- ...",3
-78444893,2021-02-04 16:49:34.972,Create live figma embed for form-group submit button behavior,"Based on my confusion of some documentation, I thought it would be worthwhile to add some visual clarity to what we're explaining, specifically for behaviors.",2
-78193008,2021-02-01 10:22:17.161,Update Figma tooltip component with Variant,"
-
-### Description
-
-
-
-I worked a lot recently with a tooltip. I found that the current component is not very easy to use because:
-
-1. I need to detach it every time because the container doesn't auto grow with the text
-1. After detach, I need to resize it and not very easy to keep the spacing manually
-1. I need to hide/show arrows in the layers instead of using a variant
-
-So I updated the tooltip component structure with variants, now it can auto grow, two lines just need to hit enter and use different arrow position can be chosen from variants manual on the right-hand side. Please see the picture below :point_down: or watch this [`video intro`](https://www.loom.com/share/bd509b045e8e41f5ae4eb29fc22fb32f).
-
-
-| Current component | Updated component by using variants |
-| --- | --- |
-|  | |
-
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/nmpl8tphpsmcDlMYfiviOS/Tooltip-component-update-Pajama-805?node-id=1%3A2)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [ ] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [ ] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [ ] **Maintainer**: Review and approve assignee’s changes.
-1. [ ] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [ ] **Assignee**: Move your working file to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [ ] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",2
-77550425,2021-01-20 14:23:00.232,chore: Point gitlab-ui status links to Storybook,,2
-77176298,2021-01-13 16:46:21.198,Guideline to open help links in new tab or not,"In the [helping users](https://design.gitlab.com/usability/helping-users) section of the pajamas, we make use of two kinds of text links. While it's clear what the text should be, there's no guideline whether that link should open in a new tab or not.
-
-We do however have some general guidelines about [external links](https://design.gitlab.com/product-foundations/interaction/#links-to-external-resources).
-
-## More details
-
-I personally am in favor of the new tab functionality, and this makes sense for GitLab.com where we now redirect all help links to the external site https://docs.gitlab.com.
-
-For self-managed instances however, the help links still point to the `/help` page of the instance.
-
-## Accessibility issues
-
-Best practice for accessibility by default is to use native browser behavior and open in the same window.
-Once `target=""_blank""` is used it disables all other browser options, so it’s best to let the user choose.
-
-## Resources
-
-- https://css-tricks.com/use-target_blank/
-- Docs guidelines on links https://docs.gitlab.com/ee/development/documentation/#linking-to-help",1
-76702013,2021-01-04 14:19:33.381,Form: multi-column/row of grouped options in forms,"### Background
-
-This is an issue created based on [another issue](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues). Before we document something we agree on, we want to explore different solution options.
-
-### Problem
-
-In some areas, the user needs to set up complicated settings, such as variable sets with some details fine-tuning. Each variables settings is a group, and users need to see them together to have a better overview or comparing different variable groups.
-
-The design needs to be flexible for desktop and mobile, easy to read and identify the groups.
-
-| Example 1 | Example 2 |
-| --------- | --------- |
-|  |  |
-
-
-
-### Solution
-
-| Option 1 - Row grouping | Option 2 - Column grouping | Option 3 -??? |
-| --------- | --------- | -------- |
-|  |  | |
-| | | |",3
-76385293,2020-12-22 13:01:27.956,Examples are sometimes loaded from an incorrect component,"In https://design.gitlab.com/components/accordion/code, the examples are loaded from `GlAccordionItem` instead if `GlAccordion`.",1
-73936334,2020-11-05 19:45:18.779,Content section > Determine how to dedupe documentation with doc styleguide,"# Problem
-
-There are currently multiple places where we have content guidelines including:
-
-* Pajamas: [Punctuation](https://design.gitlab.com/content/punctuation), [Terminology](https://design.gitlab.com/content/terminology), [Voice and tone](https://design.gitlab.com/content/voice-tone)
-* Docs: [Styleguide](https://docs.gitlab.com/ee/development/documentation/styleguide.html)
-* Handbook: [Styleguide](https://about.gitlab.com/handbook/style-guide/), [Markdown](https://about.gitlab.com/handbook/markdown-guide/)
-
-There is repeated content in all of these sections, making it difficult to know when to go where for what.
-
-We've started trying to harmonize this content between the different areas, which is resulting in content that is not DRY. For example, see https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26326 and https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2148.
-
-Tech writing has started to look at both styleguides and align them here: https://gitlab.com/gitlab-org/gitlab-docs/-/issues/636. However, we need to determine the IA in order to ensure that we are not continuing to duplicate content over time.
-
-# Solution
-
-Determine how to dedupe content docs in all various locations. This could include:
-
-- Moving all content docs to one area
- - Pros: Everything is in one place, you always know where to go to find what you need. Content isn't duplicated.
- - Cons: There are separate use cases for docs and product, so the documentation in this section could be expansive. Good IA would be needed so its easy to find details.
-- Keeping documentation docs and product docs separate, with clear cross-linking as needed.
- - Pros: Separation of concerns could make it easier to find detailed docs as needed
- - Cons: A lot of content overlaps, so it may be difficult to fully dedupe and could mean lots of cross linking and jumping back and forth between sections.",8
-73807957,2020-11-03 14:54:40.845,Move calendar icon in date picker,"Per @cam.x’s great suggestion in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/726#note_432971319, consider moving the calendar icon to the left of the date picker input.
-
-**Benefits**
-
-- Aligns with how the search input is handled.
-- Provides more room on the right to use the clear × option.
-
-
-
-/cc @gitlab-com/gitlab-ux/ux-foundations",2
-72858125,2020-10-16 23:12:12.730,Add lock-solid to GitLab UI Kit for Figma,"
-
-### Description
-
-
-
-When switching between  and  there is not enough visual distinction to quickly identify if something is locked or unlocked.
-
-:new: icon 
-
-🤚Blocking Merge Request 
- https://gitlab.com/gitlab-org/gitlab-svgs/-/merge_requests/632
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/nLyPs9zeRPQUAAmKckfLjM/Icon-lock-solid?node-id=125%3A35)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [ ] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [ ] **Maintainer**: Review and approve assignee’s changes.
-1. [ ] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [x] **Assignee**: Move your working file to the shared Figma project:
- 1. [x] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [x] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",1
-72834541,2020-10-16 12:41:20.757,UX Foundations > Pajamas OKR exploration,"During a recent conference, Design Systems & DesignOps, one of the self-work times was dedicated to thinking through what OKRs could look like for your design system. We were given about 40 minutes total to complete a list and then discuss in a small group. These were a few that came to mind, and I found it very helpful to think through objectives specific to the system itself.
-
-Feel free to add your own, and perhaps we can have further exploration on a few of these. All of the below ramp up to a larger objective of making the product more beautiful, performant and accessible for users, while providing clear _foundational_ answers to common questions so that designers can focus on designing and not on rehashing what should be “boring” decisions. A reoccurring phrase from the workshop was “align the easy thing to do with the right thing to do,” which I think aligns with our goal of building foundational things for the team to build on.",1
-72338921,2020-10-07 16:28:24.133,Dropdown component - Standardising on how to clear selection,"## Problem
-
-- From this discussion: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/43050#note_422606858
-- There doesn't seem to be a standard way to clear the selection from a dropdown
-- For example, in Value Stream Management, the following approach was used...
-
-
-
-## Proposal
-
-Standardise on a solution for clearing the selection from a dropdown:
-1. Document approach
-1. Add functionality at the component-level
-
-There are a few ways of going about it...
-
-### When dropdown is open, the Action area for ""clear selection""
-
-| Single selection | Multi selection |
-| ------ | ------ |
-|  |  |
-
-
-### after dropdown closes, the action to ""clear selection""
-| Single selection | Multi selection |
-| ------ | ------ |
-|| |
-
-
-Original proposal
-
-| Dropdown open clear button | Dropdown closed clear button | Top-level selection clears |
-| ------ | ------ | ------ |
-|  |  |  |
-
-
-@gitlab-com/gitlab-ux/designers",3
-72079844,2020-10-02 13:45:12.687,Mini progress/gauge indicator,"# Problem
-
-- Current use case: We need to visualise the progress of adoption of individual GitLab stages side-by-side
-- General challenge: visualising progress as a percentage or within some target bounds
-
-# Solution
-
-- [Figma file →](https://www.figma.com/file/M04p4bPdJSRLJJxZ8DhgmA/Mini-gauge?node-id=785%3A161)
-- Create a mini gauge chart that can fit within tables or metric boxes
-- Need to be able to look good side-by-side
-
-
-
-# MVC iterations
-
-1. Implement mini gauge variant with icon (no bounds)
-1. Implement mini gauge variant with metric (no bounds)
-1. Implement mini gauge variant with target bounds",3
-71028980,2020-09-11 13:48:52.161,WIP: Add complex List Item components to Pajamas,"
-
-### Description
-
-Currently, in Pajamas, the ""List"" component(s) that are defined speak mostly to the Markdown list and don't include complex list items as seen throughout the product. To address this, I suggest we make 2 large scale changes:
-
-1. Move the current list descriptions to the `Typography` section of Pajamas.
-1. Update the List components to include complex list items as displayed throughout the product (see examples below).
-
-##### Examples
-
-| Issue list view |
-|---|
-||
-
-| Package list view |
-|---|
-||
-
-
-### Figma file
-
-
-
-[View working file in Figma →](ADD LINK TO FIGMA FILE/FRAME)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [ ] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [ ] **Assignee**: Update the link to the working file in the issue
- description.
-1. [ ] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [ ] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [ ] **Maintainer**: Review and approve assignee’s changes.
-1. [ ] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [ ] **Assignee**: Move your working file to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [ ] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",13
-70889051,2020-09-08 16:55:49.679,UI Kit > Add inline code and code blocks,"
-
-### Description
-
-Based on the UI changes in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26731, adding styles/components to the component library for:
-
-* [x] Inline code
-* [x] Code blocks
-
-### Out of scope
-
-* Appearance of code when not using the default theme preference.
-* Dark UI.
-* Other inline text elements (See https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/680)
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/omuzKJD8RKLPpqv24CUUyS/Component-Inline-code-and-code-blocks?node-id=1%3A70)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [x] **Assignee**: Move your working file to the shared Figma project:
- 1. [x] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [x] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [ ] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",1
-70886070,2020-09-08 15:55:39.441,Make responsive segmented control,"### Problem
-
-Currently our [segmented control component](https://design.gitlab.com/components/segmented-control) isn't very responsive on small screens when the component has many options (see below screenshot).
-
-
-
-We don't have a current design for how to fix this.
-
-### Proposal
-
-Some possible solutions:
-
-- [Vertical variation for button groups](https://bootstrap-vue.org/docs/components/button-group#vertical-variation)
-- Wrapping the component
-- Making the last button a dropdown with the extra options inside of it.
- - ",3
-70830391,2020-09-07 14:39:08.013,"KR: Communicate component lifecycle improvements to the UX department => 0%, TBD","Related to [Clarify the Pajamas component lifecycle process](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/1)
-
-Key result: Communicate component lifecycle improvements to the UX department (slack, UX weekly announcement).",1
-70830214,2020-09-07 14:36:36.911,"KR: Improve the component checklist by adding links/references to the necessary steps to complete the lifecycle, and move it to the Pajamas project. => 0%, TBD","Related to [Clarify the Pajamas component lifecycle process](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/1)
-
-Key Result: Improve the component checklist by adding links/references to the necessary steps to complete the lifecycle, and move it to the Pajamas project.",1
-70744870,2020-09-04 16:23:21.236,Skeleton loader for Releases,"
-
-### Description
-
-
-
-In https://gitlab.com/gitlab-org/gitlab/-/issues/201959/ we will introduce an update to the ~""component:skeleton-loader"" of the Releases page. This issue adds a variation of the gilab-ui component so that users can be able to see a loading state that always represent Releases in a recognizable way.
-
-- The component variation should be called: `release-card-skeleton-basic`.
-- I propose adding the UI to the Product Pages figma file.
-
-### Figma file
-
-
-
-[View branched working file of Component Library →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/EIhkW34nsNcpDXLKQNte4w/Component-library?node-id=2844%3A3)
-
-[(Old) View working file in Figma →](https://www.figma.com/file/9Uee1fu4GrNrEhCHRTi2nK/Release-page-skeleton-load-gitlab-201959?node-id=1%3A2)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [-] **Assignee**: Move your working file to the shared Figma project (file was a branch, so archived by the maintainer using the branch feature).
-1. [-] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [-] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [-] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",2
-70208931,2020-08-24 11:09:35.005,Make mermaid diagrams work in Pajamas,"This is a Follow-up from ""Draft: docs(contribute): Move component lifecycle up"" https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2053/
-
-Currently, Pajamas does not render mermaid diagrams in markdown pages.
-
-Mermaid diagrams render as *code blocks* in markdown files. This is a useful tool for generation of diagrams and flowcharts from text, instead of using static images in the design docs pages.
-
-See https://docs.gitlab.com/ee/user/markdown.html#mermaid",5
-70023441,2020-08-19 16:12:01.391,Pajamas pages break if a Vue component doesn't exist in component_documentation.js,"Recently, the dropdowns page was broken due to `GlNewDropdown` no longer existing under [`component_documentation.js`](https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/1637/diffs#d836144972fdb1c81b2724a1b894dec15e0973f4_62_62), which Pajamas pulls from when checking if a vue component conforms to the design system [`followsDesignSystem`](components/componentinfo.vue).
-
-MR that fixed the broken page: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2050",1
-69979688,2020-08-18 21:31:07.000,UI Kit > Create inline text element components,"## Problem
-
-Several inline text elements need to be added to the component library in Figma. We need to determine where they best fit since they can cross over between UI and markdown.
-
-
-
-## Solution
-
-* Audit the product to find inline elements that can’t be created with styles alone (the ones in the image above have backgrounds).
-* Create components for each inline variant.
-* Determine the best location in the component library and publish the additions.
-
-/cc @tauriedavis
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/YJWAkSuSBsEaIWMbYftE5x/Component-Inline-text-components?node-id=1%3A70)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [x] **Assignee**: Move your working file to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] **Assignee**: When applicable, create a merge request in this repository
- with the [component-guideline template][component-guideline-template]
- to create or update the component’s documentation page.
-1. [ ] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",2
-69807043,2020-08-13 14:30:26.698,Allow linking to component usage for all region components.,"### Problem
-We cannot directly navigate to the Vue component usage section in all region components like [Empty State](https://design.gitlab.com/regions/empty-states/) by visiting `https://design.gitlab.com/regions/empty-states/code` as the url returns 404.",2
-69284313,2020-07-31 08:16:37.509,Document established onboarding & educational patterns: nudge,"Document the findings and learnings from the [suggest a pipeline experiment](https://gitlab.com/groups/gitlab-org/growth/-/epics/14). Based on these learnings, establish a pattern for onboarding and educational purposes, so that other designers can reuse it.
-
-By the time I'll start working on documenting these we'll have run numerous variations of this experiment: different initial nudges, different copy.
-
-Include details about:
-
-* reference the FOGG behaviour model
-* components that can be used
-* variations of initial nudges and recommendations on when they should be used
-* recommendations on the number of steps
-* recommendations for writing copy and providing context (why the nudge is shown, what value will the user get from it)
-* should only be done to benefit the user",5
-68821525,2020-07-21 18:21:52.775,Update empty state documentation to include details about existing controls,"As part of discussion on https://gitlab.com/gitlab-org/gitlab/-/issues/229636#note_382613266 and https://gitlab.com/gitlab-org/gitlab/-/issues/229350, we realized that we could use a little clarification in our empty state documentation.
-
-When we have an empty state, should the page controls still appear, but be disabled? Or, should they be completely hidden?
-
-We currently have both situations in our empty states. Should we clarify when the controls appear, and why?",2
-62159621,2020-07-16 22:33:44.649,Dropdowns > Audit Figma and GitLab UI component,"Review dropdowns in Figma and GitLab UI to ensure parity
-
-If issues are found, create issues and mark them as blockers to this issue.
-
-- [ ] All variations exist in Figma and GitLab UI
-- [ ] Styling in Figma matches GitLab UI
-- [ ] All related issues are closed
-- [ ] Status table in Pajamas is updated and accurate",3
-52422757,2020-06-30 18:28:03.741,GitLab UI examples > Add knob options,"On the vue tab for components, you should be able to interact with gitlab ui knobs",5
-52354157,2020-06-30 16:30:31.126,feat(skeletonloader): Extend usage of Skeleton loader vs. Spinner usage,"Clarify when to use spinner vs. skeleton loader in different scenarios.
-
-From thread https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35265#note_368474339",2
-50091551,2020-06-25 18:41:59.075,Audit principles page,"We have a lot of content on our principles page, including some guidelines. There is note that states our current principles may not follow the guidelines. We need to audit this page and determine what changes, if any, need to occur to the principles and/or guidelines",3
-42999400,2020-06-12 07:57:22.736,Mobile layout has double padding on left/right,"From https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/1963#note_359198356
-
-`content` adds left/right padding which was getting doubled, so narrow screens have extra padding
-
-We can probably move the `.content.limited` rule to `.limited` to fix this
-
-",1
-35473730,2020-06-05 10:38:08.164,Pajamas UI Kit > Gauge chart,"
-
-### Description
-
-Gauge chart visualization is useful for monitoring the status of a metric in real time, and to quickly convey the status of the metric in relation to the ranges or a threshold set by the user. A gauge chart is a single metric chart.
-
-#### Example use case
-
-An SRE viewing metrics in the Metrics dashboard when investigating an incident. A gauge chart instantly communicates to the user the status of the metric, even when viewed at a small size. At a glance the user understands whether the value is falling within an acceptable range.
-
-#### Requirements
-
-- The chart should clearly communicate the current value and show where that value falls within the ranges set by the user (2 or 3 ranges can be set).
-- Users can set alerts on the metric, so we need to make sure that when the alert is firing it's immediately visible
-- The value ranges don't have to coincide with the alert threshold. The user should be able to set an alert for any value regardless of what range it falls into
-- The chart should be readable even at a very small size. It's not uncommon for our users to have multiple gauge charts crammed into a small dashboard area to form a ""speedometer"" of sort. Check out [one of the GitLab dashboards ](https://dashboards.gitlab.com/d/sv_pUrImz/ci-autoscaled-machines-metrics?orgId=1&refresh=5m&from=now-30d&to=now&var-dc=All&var-runner_group=All&var-cpu_mode=nice)for an example. Currently, GitLab Metrics charts aren't resizeable, but they will be in the future.
-
-#### States/ variants
-
-- [x] Alert set
-- [x] Alert firing
-- [x] Low range, mid range, high range
-- [x] Large (expanded chart view)
-- [x] Small (50%)
-
-### Additional details
-
-We will be building the chart using the [Gauge e-charts component.](https://echarts.apache.org/examples/en/editor.html?c=gauge)
-
-Notes for the docs:
-- Leave a note in the component description that states that the header is mandatory but the size should vary depending on page content/hierarchy.
-
-
-
-
-
-### WIP Proposal
-
-| Medium range | With an alert | With a firing alert |
-| ------ | ------ | ------ |
-| |  |  |
-
-### Figma component
-
-[View component in Figma →](https://www.figma.com/file/rxA1gTpS6L7wMhAs9rZnaU/Gauge-chart?node-id=0%3A1)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Create component in your own draft file in Figma using the
-[component template](https://www.figma.com/file/OmvFfWkqEsdGhXAND133ou/%5BComponent%5D),
-including all variations and states.
-1. [x] **Assignee**: Update the link to the Figma file in the issue description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer](https://about.gitlab.com/company/team/?department=fe-ux-foundations-team)
-to review your component (ensure they have edit permissions in Figma).
-1. [ ] **Reviewer**: Review and approve assignee’s addition. Ensure that design
-includes all variations/states.
-1. [ ] **Reviewer**: Assign to a [Figma maintainer](https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com) for final review (make sure they have edit permissions in Figma).
-1. [ ] **Maintainer**: Review and approve assignee’s addition.
-1. [ ] **Maintainer**: Add the design to the **Pajamas UI Kit** file, ~~and view
-the component in the Assets panel to ensure it aligns with what’s outlined in the
-[document and asset library structure](https://gitlab.com/gitlab-org/gitlab-design/-/blob/master/CONTRIBUTING-Figma.md#document-and-asset-library-structure) documentation.~~ (Not applicable for the chart.)
-1. [-] **Maintainer**: Publish the library changes along with a clear commit message.
-1. [ ] **Assignee**: Move the draft file to the **Component archive** Figma project. If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [ ] **Assignee** (or Maintainer, for community contributions): If it's a new
-pattern or a significant change, add an agenda item to the next UX weekly call
-to inform everyone.
-1. [ ] **Assignee**: Create a merge request in this repository with the [component-guideline template](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md)
-to create or update the component's documentation page. Link it here as a related
-merge request. Use `View design in Pajamas UI Kit →` for the link text. This replaces
-any link to Sketch Measure specs. Anyone with the link should be able to view the file.
-1. [x] **Assignee**: [Create an issue in GitLab UI](https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new)
-to build or update the component. Mark the new issue as related to this one.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.",3
-34251371,2020-05-07 08:20:26.831,feat(filters): Research scroll behavior for filters,"In https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/1343 @matejlatin highlighted filters issue with scrollbar on OS X:
-
-
-
-pretty acceptable in Linux & Windows with other scroll type:
-
-
-
-We need to research the proper way of handling a lot of scrollable content in filters.",3
-33963045,2020-04-29 17:12:08.465,Add additional chart information to to PJs,"### Description
-
-PJs doesn't include all chart options available from within gitlab-ui.
-
-#### Examples
-
-https://design.gitlab.com/components/charts#types only mentions column charts, line charts, and area charts.
-
-In addition to these, we also have:
-
-* Scatter chart
- * https://gitlab-org.gitlab.io/gitlab-ui/?path=/story/charts-discrete-scatter-chart--default
-* Heatmap
- * https://gitlab-org.gitlab.io/gitlab-ui/?path=/story/charts-heatmap--default
-
-Column charts also support a click interaction - I don't actually think that this is explicitly mentioned in gitlab-ui either.
-
-#### Additional information
-This was raised in discussion over here https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541#note_333095362",4
-33865614,2020-04-27 16:12:27.424,PJs component page template: re-evaluate content based on JTBDs,"## Overview
-
-Let's re-evaluate the content (and structure) of the PJs component page template to improve the utility and usability for GitLab designers, devs and PMs. This is related to the broader PJs information architecture challenges mentioned in gitlab-org/gitlab-design#798.
-
-The best way to prioritise, manage and refine the content on the page is by using Jobs to be done.
-
-## Problem
-
-The main pain points I found with component page templates today:
-
-- **Text-heavy** - PJs is much more text-heavy than most other design systems. Much of the text content could be replaced with images and demos. The large amount of content makes it hard to scan and find the information I'm looking for.
-- **Usage guidance vs implementation guidance** - Content on implementation guidance ([as discussed here](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/536)) is left in the usage guidelines - adding to the text-heaviness. This also reduces the clarity on the usage guidance in general.
-- **Burying the lead** - The current structure is setting pages up in a way where the demo is at the bottom of the page behind a bunch of text which may or may not be relevant for your use case. A new structure is required which front loads the demo and dives into details later. Following similar ideas to the [Minto Principle](https://medium.com/lessons-from-mckinsey/the-pyramid-principle-f0885dd3c5c7).
-- **Additional content** - We also have a lot of other content that could be interesting to include in a design system as stated in [this comment](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1111) - this doesn't need to be shown on the page, but could at least be linked, so we see the thought and rationale that has gone into designing the component
-- **Variation** - There a lot of inconsistency in how component usage guidelines are written.
-
-## Idea
-
-> “If a picture is worth a thousand words, a prototype is worth a thousand meetings” - **David Kelley, IDEO**
-
-Some general principles for laying out these pages:
-- **JTBD & role-informed** - We should differentiate sections and prioritise what content goes on the page based on what our primary personas are trying to achieve
-- **Demo-heavy** - We should front-load our component pages with visual content and demos for a quicker understanding
-- **Show me > tell me** - We should strip away as much text as possible in favour of demos and programmatically embedding rules, styles and interactions
-- **On-page nav** - We should have on-page navigation for quicker access to particular sections
-- **Standardise component usage sub-sections** - We should standardise on component usage sub-sections to improve consistency and clarity (e.g.[IBM carbon](https://www.carbondesignsystem.com/components/date-picker/usage#content) standardized on component variations, content guidelines & interactions/functionality). This also makes it easier to spot whether any functionality or styles are missing.
-
-I think [IBM Carbon](https://www.carbondesignsystem.com/) and [Salesforce Lightning](https://www.lightningdesignsystem.com/) are both great examples of prioritising which JTBD they want to satisfy for designers & devs without being too text-heavy.
-
-## Jobs to be done
-
-Create a ranked list of JTBD to prioritise content on the page:
-
-| Title | Situation | Motivation | Desired outcome | Persona |
-| ------ | ------ | ------ | ------ | ------ |
-| **General usage guidance** | When I am unfamiliar with a component, | I want a quick and high-level overview of the what the component looks like, how it works and its most popular use cases, | so that I know whether or not I should use it. | All |
-| **Design tool component** | When using a component, | I want a representation of that component in Figma/Sketch | so that I can quickly work with it in my designs | Designer |
-| **Detailed usage guidance** | When using a component, | I want to understand details of variations, style, functionality and accessibility | so that I use the component in the way it was designed | Designer |
-| **Component usage in the product** | When using a component, | I want to where else in the product it is being used, how much it is being used and for what use cases, | so that I | All |
-| **Design decisions** | When using a component, | I want to understand how research, discussions & usage helped decide on a specific design, tenet or guideline | so that I understand why the component was designed in that way | Designer |
-| **Component gaps** | When using a component, | I want to understand whether this current iteration of the component has the variations, style, additional functionality and accessibility required for my use case | so that I know whether we should update it or not | Designer |
-| **Component pipeline** | When using a component, | I want to see if there are any new components or updates in the pipeline | so that I can utilise the component or collaborate with the person who is working on it | Designer |
-| **Component development guidance** | When building components, | I want to understand what patterns should be embedded into the component programmatically | so that the component works in the way it was designed. | Developer |
-| **design.gitlab, GitLab-ui & figma/sketch sync** | When using a component, | I want to be sure that the component variations, style, additional functionality and accessibility in design.gitlab reflect what is shown in gitlab-ui and figma/sketch | so that I have an accurate representation of what's available and continuity of understanding with other roles in my team | All |
-| **Add/edit component** | When reviewing PJs and I see missing/incorrect component content | I would like to add/edit content | so that I contribute to refining our design system | Designer |
-| **Integrating component** | When I am integrating a component in our [component lifecycle](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/blob/master/doc/component-lifecycle.md) | I want to ... | so that ... | Developers |
-
-## Process
-
-1. **Gather** - Use this issue to collate what the primary the JTBD for designers, devs, PMs, technical writers, researchers
-1. **Prioritise** - Prioritise the JTBD to prioritise the content in PJs
-1. **Create template** - Create a new content template based on our prioritisation
-1. **Create vision mockup** - Create a new vision mockup of what PJs component pages could be
-
-## Additional ideas
-
-- On page table of contents
-- Additional tabs
-- Changing structure of pages to front-load demos and visual content at top of page
- - First step would be changing component template file: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/pages/components/template.md
-
-## Proposal
-
-- Determine a new structure that allows users to easily find the content they are looking for. The end result of this issue should be working page templates and consistent sections and language.",8
-33393960,2020-04-16 17:28:55.972,Add contrast info to neutral color palette,"The following discussion from !1787 should be addressed:
-
-- [x] @pedroms started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/1787#note_322602636): (+2 comments)
-
- > @jeldergl should we also add the `Passing level and contrast ratio` information to the neutral palette?",1
-33058352,2020-04-08 17:00:57.725,Communicating code coverage of each component,"In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/1804, the status of components that already live inside the GitLab product were moved to `Integrated`.
-
-I'm curious to hear what would be helpful on the status page. A lot of questions I get are related to why a component in production does not match Pajamas. Even if a component already lives in the product, that does not mean they are fully integrated or used in every instance. How should we be communicating the code coverage of each component? Should that live inside the status page? How can we feasible track this over time?",5
-32794334,2020-04-02 16:59:02.898,Add more clarity around bold 600 decision,"Its not clear from looking at pajamas what font weight we use for bold text. You have to inspect the text or find the variable in GitLab UI.
-
-We should include the variable name and it's value on the typography page. We can also include explanatory text that explains why we use 600 over 700
-
-> It’s because some system fonts have a semi-bold, which would be mapped to 600, and that weight was preferred. For system fonts without a semi-bold it would be mapped to the 700 weight, which is why it could look extra bold in other OSs.",1
-32537602,2020-03-27 12:47:48.959,Add accessibility guidelines and specs for the filters,"gitlab-org/gitlab-services/design.gitlab.com!1744 adds the usage guidelines, next we need to think how to properly build the filter components so that they're accessible. Let's add those guidelines and specs to the Pajamas after that.",3
-35324648,2020-03-19 18:51:00.547,Figma region > Empty states,"
-
-
-
-
-
-[View component in Figma →](https://www.figma.com/file/Bp0HvnbtcLcoLYHXbrWwzc/Empty-states?node-id=0%3A1)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Create component in your own draft file in Figma using the
-[component template](https://www.figma.com/file/OmvFfWkqEsdGhXAND133ou/%5BComponent%5D),
-including all variations and states.
-1. [x] **Assignee**: Update the link to the Figma file in the issue description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer](https://about.gitlab.com/company/team/?department=fe-ux-foundations-team)
-to review your component (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s addition. Ensure that component
-includes all variations/states and, if applicable, matches existing Sketch specs and
-is responsive.
-1. [x] **Reviewer**: Assign to a [Figma maintainer](https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com) for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s addition.
-1. [ ] **Maintainer**: Add the component to the **Pajamas UI Kit** file, and view
-the component in the Assets panel to ensure it aligns with what’s outlined in the
-[document and asset library structure](https://gitlab.com/gitlab-org/gitlab-design/-/blob/master/CONTRIBUTING-Figma.md#document-and-asset-library-structure) documentation.
-1. [ ] **Maintainer**: Publish the library changes along with a clear commit message.
-1. [x] **Assignee**: Move the draft file to the **Component archive** Figma project. If you're a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [ ] **Assignee** (or Maintainer, for community contributions): If it's a new
-pattern or a significant change, add an agenda item to the next UX weekly call
-to inform everyone.
-1. [ ] **Assignee**: Create a merge request in this repository with the [component-guideline template](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md)
-to create or update the component's documentation page. Link it here as a related
-merge request. Use `View design in Pajamas UI Kit →` for the link text. This replaces
-any link to Sketch Measure specs. Anyone with the link should be able to view the file.
-1. [ ] **Assignee**: [Create an issue in GitLab UI](https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new)
-to build or update the component. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
----
-
-## Empty state examples
-
-* https://www.carbondesignsystem.com/patterns/empty-states-pattern/
-* https://stackoverflow.design/product/components/empty-states/
-* https://www.lightningdesignsystem.com/guidelines/empty-state/#site-main-content",3
-86304066,2020-03-18 04:24:58.393,Form help and error text should not be separate,"## Problem
-
-For our form elements, help text and error text are currently defined as two separate text items. This could be confusing as error text could be partially duplicative of the help text. Depending on how the help text is tied to the input for accessibility, this could also add confusion, or cause some info to be missed. Because the help text remains gray, it visually feels disconnected with an input in error state.
-
-## Solution
-
-Help text is a single, dynamic text block with the potential for multiple states.
-
-* By default it is instructional and in a neutral palette
-* When an error occurs the help text becomes more explanatory so that a user knows how to correct the error. The danger palette is used.
-
-In this case there is inly one help text block for instruction and error prevention.
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-
-/cc @uhlexsis @tauriedavis @pedroms",1
-31850907,2020-03-10 23:50:22.128,"Combine contents of ""Vue component"" and ""Design"" tabs into a single page","There is often duplicated content between the tabs. For example: ""Alerts allow the application to pass along relevant system information to the user without impeding their journey. Alerts are system generated and may or may not be derived by a user’s action."" is the same in the following two places:
-
-
-
-
-
-Instead of a tab, we can add a ""Component"" section to the design tab (and then remove the tabs altogether)",8
-31691849,2020-03-06 19:42:44.993,GitLab UI components demos: Reduce style inconsistencies between Storybook and design.gitlab.com,"# What problems are we trying to solve here?
-
-## 1. `.md` styles leaking into GitLab UI components demos
-
-`design.gitlab.com` has a set of typography CSS rules being applied on several common HTML elements in the `.md` scope: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/5f1e9246192f9f04dcd50cefa55985d63c0f88ce/assets/stylesheets/framework/_typography.scss#L35-81
-
-This has been causing issues with components demos as they are being displayed into the same scope, resulting in some components inheriting unexpected CSS rules, an example is the `GlBanner` component: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/1620#note_245401786
-
-This has led us to explicitly setting more and more CSS rules in components stylesheets, solely to override `.md` styles. We have tried to circumvent this specific issue by [wrapping components in a custom element](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/1737) where GitLab UI styles would be injected in the Shadow DOM. While this solution was promising as it stopped all CSS leak issues, some components like tooltips and popovers aren't Shadow DOM-ready and aren't able to render when they don't have access to the global `document`. More generally, this approach brought us back to problem `#2`.
-
-
-## 2. Styling elements in the global scope
-
-To prevent GitLab UI's styles from conflicting with `design.gitlab.com`'s styles, we have scoped its styles to the `.app-styles` class: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/5f1e9246192f9f04dcd50cefa55985d63c0f88ce/assets/stylesheets/app.scss#L33-36
-
-This lets us apply components styles locally, without affecting the rest of the website.
-
-This is a sensible approach but we've reached its limits as some components are appending elements to the `body` in the global scope. Since those elements are escaping the `.app-styles` scope, they can't be styled properly, unless we can come up with specific workarounds. For example, we've been able to preserve styles for the `GlModal` component by adding the `.app-styles` class to its wrapper element: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/5f1e9246192f9f04dcd50cefa55985d63c0f88ce/layouts/default.vue#L103-114
-There are other cases, like the `GlToast` component, where there is no obvious workaround that we can apply, resulting in a broken looking element in the demo:
-
-
-
-Overall, we should try to make it as easy as possible to include components demos in `design.gitlab.com`. Having to come up with workarounds makes for a poor developer experience.
-
-# How can we address these issues?
-
-## 1. Prevent `.md` styles from leaking too deep in the DOM
-
-To prevent `.md` styles from affecting too many of their children, let's make sure that the CSS rules only apply to direct children in `.md`. This will prevent the CSS from leaking into component demos, reducing the need for explicitly setting CSS rules in GitLab UI to override Pajamas' styles.
-
-This approach has a downside: Markdown elements can be nested. For example: `> ### A title in a blockquote`. By applying styles on direct children only, those nested elements will not be styled properly. Since Pajamas doesn't seem to contain any nested Markdown element at the moment, this fix should be acceptable considering its benefits outweigh its disadvantages.
-
-MR: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/1753
-
-## 2. Apply GitLab UI styles globally
-
-TBD
-
-MR: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/1740",3
-30733784,2020-02-13 21:33:01.456,Remove radios vue banner and set status to Built,"1. In Pajamas docs, remove the banner on vue tab that warns of incorrect styling
-1. In Pajamas docs, set the status to `Built`",1
-53985995,2020-01-23 22:52:10.589,Figma component > Add Card,"
-
-
-
-
-
-[View component in Figma →](https://www.figma.com/file/RbS6MpYuRWGvcdxRlUGxAD/Cards?node-id=1%3A496)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Create component in your own draft file in Figma using the
-[component template](https://www.figma.com/file/OmvFfWkqEsdGhXAND133ou/%5BComponent%5D),
-including all variations and states.
-1. [ ] **Assignee**: Ask another Figma Pilot Designer to review your component (make sure they have edit permissions).
-1. [ ] **Reviewer**: Review and approve assignee’s addition. Ensure that component
-matches Sketch specs, includes all current variations and states, and (if applicable)
-is responsive.
-1. [ ] **Assignee**: Add the component to the **Globals - beta** file, and view
-the component in the Assets panel to ensure it aligns with what’s outlined in the
-[Figma structure for library](https://gitlab.com/gitlab-org/gitlab-design/issues/791) issue.
-1. [ ] **Assignee**: Publish the library changes along with a clear commit message.
-1. [ ] **Assignee**: Update component link in the issue.
-1. [ ] **Assignee**: Move your draft file to the **Component archive** Figma project.",3
-29712647,2020-01-17 18:48:44.957,Fix fonts size of help text in radios/checkboxes,"The following discussion from !1651 should be addressed:
-
-- [ ] @pedroms started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/merge_requests/1651#note_271309985): (+4 comments)
-
- > @jboyson unsure if related to this MR, the help text paragraph `p` has an odd font-size:
- >
- > ",1
-105457393,2022-03-24 21:00:12.515,Figma: Change GitLab logo in file thumbnails,"Update the logo in file thumbnails (cover slides) starting with publicly shared files in the Pajamas UI kit and then the other cover template.
-
-
-
-",1
-105236024,2022-03-21 21:27:21.078,UI Kit > Add GitLab tier badge variant,"
-
-### Description
-
-
-
-Following https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1242 and https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2728#note_862246994 we should add a GitLab tier badge variant to GitLab UI.
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/H45tzHETZOwB7kJh3YqKj0/Component-library?node-id=19947%3A350E)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [ ] **Assignee**: If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, please consider [transfering ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] **Assignee**: When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] **Assignee**: When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-104621769,2022-03-11 14:40:50.808,Discussion: Add guidelines for alternate visual treatment for links,"## Problem
-
-We have the visual treatment for links identified in the GitLab UI, but do not have a dedicated section under Pajamas guidelines to specify them. Today, we treat `copy blue with an underline` as a standard and desired state for links, but from recent feedback on Verify features, we were able to surface a need for multiple visual treatments for the same.
-
-There are pages in the product that list resources, and for their contextual identification it is vital to retain links to associated resources. Example- a pipeline can be best identified in the presence of the commit name/number, branch name, merge request details and triggerer information. Not every user would make use of all of these link, but the personas interacting with these pages are varied and through research we have learn that removing any of these information can prove to be disruptive to a huge number of users.
-
-Presence of many different links as a group, with each demanding user's attention can turn out to be very visually disorienting. To combat this discomfort, we should consider providing different visual treatments to those links. For example - the link that belongs to the resources that is primary to the page can have a blue color, while for the other links we can go for a subdued visual affordance, ma be dark gray with an underline?
-
-We are already doing this on a few pages, such as issues, where we do not give a blue color to link, and at other pages where many different links in a single line have different treatments. To ensure that we provide our users with a coherent experience across platforms, we should document primary and alternate treatments for links and the circumstances under which they should be used.
-
-### Use cases
-
-I'm listing use-cases from Verify since I'm more versed in those.
-
-#### Pipeline Execution: Pipeline index page
-| Image | Resources linked |
-|------------|-------------|
-|  | Commit, Merge request, Branch, Pipeline |
-
-#### Release: Environment list view
-| Image | Resources linked |
-|-------|------------------|
-| | Commit, Branch, Deployment |
-
-#### Another example of what to avoid:
-
-Links with no affordance inline with plain text. Here, they should have at least an underline, and probably different color too.
-
-| What's a link? | Links |
-|-------|------|
-|||
-
------------
-
-### Few consideration highlighted by @jeldergl in a [slack thread](https://gitlab.slack.com/archives/C010NAWPRV4/p1646921391954459):
-
-> 1. Ensure these are understood as links in context.
-> 1. See what can be done to make the gray links look more like a link.
-> 1. Be extremely clear when documenting the use case while referencing all of the factors.
-> 1. Ensure that what’s decided on and documented here can be abstracted out enough to address similar parts of the UI without creating loopholes.
-
-------------
-
-### Resources
-
-- [WCAG Success Criteria 1.4.1 Use of Color](https://www.w3.org/TR/WCAG21/#use-of-color)
-- https://gitlab-org.gitlab.io/gitlab-ui/?path=/story/base-link--default-link
-- https://gitlab.com/groups/gitlab-org/-/epics/6414
-- [UI type scale link style in Pajamas UI Kit](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=542%3A334)
-- [Documentation markdown link style in Figma](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/Type-scale---Documentation-Markdown?node-id=1%3A97)
-- [Compact markdown link style in Figma](https://www.figma.com/file/mjAZxHkK95TlQ6L14aNp2M/Type-scale---Compact-Markdown?node-id=5%3A44)
-- [Link styles (ideal state) in MR widget instances](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=38193%3A30482)
-
-_Also view linked issues_
-
-@gitlab-com/gitlab-ux/designers",5
-104591009,2022-03-11 05:08:17.551,Data visualization - Update mini pipeline graph dropdown tooltips to include trigger job instance,"
-
-### Description
-
-In https://gitlab.com/gitlab-org/gitlab/-/issues/340194 we're adding a special tooltip text to the trigger jobs tooltips to indicate they they're trigger jobs. This needs to be updated in the Data vis Figma file.
-
-
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/17NxNEMa7i28Is8sMetO2H/branch/pheBqF0DOICBa5DAqE4hID/Data-Visualization)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Merge the branch or add the changes or additions to the
- target file.
- 1. [-] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [-] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [-] **Assignee**: If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. [-] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [-] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [-] If you’re a community contributor, please consider [transfering ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [-] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [-] **Assignee**: When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [-] **Assignee**: When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-104500464,2022-03-09 17:53:17.318,ViewComponents > Determine process and documentation,"https://gitlab.com/gitlab-org/gitlab/-/merge_requests/82118 is our first MR that migrates a component helper to a ViewComponent. This could help with HAML/HTML components, but needs more exploration.
-
-Docs: https://viewcomponent.org/
-
-This issue is to help serve as discussion around View Components, how we might utilize and document them, and where that documentation should live.",4
-104478590,2022-03-09 14:09:34.699,Define standards for edit icon,"### Description
-
-We do not consistently use the same icon to represent editing an object. This is based on this [slack thread](https://gitlab.slack.com/archives/CLW71KM96/p1646833267140679).
-
-- [x] Audit edit icons (search for the pencil, pencil-square icon in the codebase)
- | pencil | pencil-square |
- | ------ | ------ |
- |  |  |
-- [x] Come up with a recommendation
- | pencil - use for edit |
- | ------ |
- |  |
-- [x] Update that icon to include `edit` definition in Figma
-- [ ] Add this in Pajamas documentation - most likely [table actions](https://design.gitlab.com/components/table#additional-actions) - [MR](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2901)
-- [ ] Replace pencil-square with pencil in GitLab UI - [MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89897)
-
-
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] Assign the correct component label to this issue.
-1. [x] Create an MR with the additions or updates needed.
-1. [ ] When applicable, [create an issue using the `Figma update` issue template][pajamas-figma-update-template] to update the component in Figma, and mark it as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template]. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",2
-103976000,2022-03-02 16:32:20.303,Popover > Unbox header,"
-
-### Description
-
-As part of an effort to ""unbox"" the GitLab UI (:arrow_forward: [watch a video with more context](https://www.youtube.com/watch?v=MxpZuWQH-kk)), the popover component could have a simple update to remove the border between the header and body content and padding. See a similar effort for [unboxing the modal](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1221).
-
-**How does this benefit the UI and support unboxing?**
-
-- The popover has hierarchy established with different font weights, the dividing border just reenforces the hierarchy that already exists.
-- Similar to the results in the modal, this also allows us to remove the extra padding needed when there are two separate sections, effectively reducing popover height.
-- Removing the border between the header and content allows for a more natural reading flow between header and content without the visual break that makes them feel less connected.
-
-
-
-### Result
-
-
-
-### Figma file
-
-
-
-[View working branch in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/a9sU9h6eO7waDKgaltWEzX/Component-library?node-id=425%3A131)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [ ] **Assignee**: If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, please consider [transfering ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] **Assignee**: When applicable, [create an MR in this repository][new-gitlab-ui-mr] and apply the ""component-guideline"" template
- to create or update the component’s documentation page. If you do not have capacity, [create an issue in this repository using the ""Component documentation"" issue template][pajamas-component-documentation-template]. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: When applicable, [create an issue in GitLab UI using the ""Component"" issue template][gitlab-ui-component-template] to build or update the component code. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[pajamas-component-documentation-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-[new-gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new",1
-103845979,2022-02-28 16:42:53.121,Dropdown > Update styles,"## Background
-
-Dropdowns (trigger button that opens a panel of options) in GitLab historically used a check icon to identify a selection. Awhile ago it was proposed to update to using literal checkbox and radio ``s to better represent the selection (single/multi-select). After more learning around what constitutes options within a dropdown, it' seems's clear that using literal form elements is _not_ ideal and doesn't reflect the semantics for options within a [listbox](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/listbox_role) or [combobox](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/combobox_role).
-
-**Current**
-
-
-
-## Proposal
-
-Update the design of options within a dropdown panel to represent a selection without using literal form elements. This can be based on the previous design and should include the following states:
-
-- Rest
-- Hover (`:hover`)
-- Focus (`:focus`)
-- Active/pressed (`:active`)
-- Selected
-
-Since multi-select is a function of the component and context, and not an individual option (that uses `role=""option""`), the design of an option can be the same for single and multi-select.
-
-**Proposed design**:
-
-
-
-- Include a tip pointing to the referring trigger.
-- Ensure the panel uses the correct [shadow](https://design.gitlab.com/layout/layers#shadows).
-- Use a small :mag: icon in the search input to help with alignment and feel more in scale with the text (might consider this elsewhere in the future too).
-- Selected item has rounded rectangle container.
-- Border radius increased on panel to keep in proportion to border radius of elements within.
-- Left aligned header.
-- Option for panel action (to clear all, unassign, etc.).
-
-### Concepts
-
-There's a matrix of options:
-
-- Edge-to-edge option vs. inset rounded rectangle. Space is the primary consideration, but more space could benefit distinguishing options at the cost of a bit more scrolling. The inset rounded rectangle would also be closer to how flyouts are handled in the left navigation.
-- Gray vs. blue selected item background. While gray keeps the UI more subdued, the use of blue aligns with our prescribed use to indicate a current or active state and also provides more differentiation with hover states.
-- Checkmark vs. border selection indicator. Space is also a consideration here, but what type of indicator makes identifying a selection quick, clear, while not impeding readability is most important.
-
-👁🗨 View initial concepts
-
-| | **Blue highlight** | **Gray highlight** |
-| ------ | ------ | ------ |
-| **Edge-to-edge checkmark ✓** |  |  |
-| **Inset rectangle checkmark ✓** |  |  |
-| **Edge-to-edge border ⎮** |  |  |
-
-
-
-🎛 View more examples for comparison
-
-| | **Blue highlight** | **Gray highlight** |
-| ------ | ------ | ------ |
-| **Edge-to-edge checkmark ✓** |  |  |
-| **Inset rectangle checkmark ✓** |  |  |
-| **Edge-to-edge border ⎮** |  |  |
-
-
-
----
-
-**Additional considerations**:
-
-
-
-1. Tip pointing to trigger element
-1. Unbox the header (shadow on scroll)
-1. Reduce header text size
-1. Universal action placement (for actions like ""Unassign"" or ""Remove all,"" etc.)
-1. Smaller search icon in search input
-1. Better left edge alignment
-1. Smaller label color swatch that also matches the label shape
-1. Increased outer border radius for inset rectangle option for accurate border radius scaling",5
-102864498,2022-02-22 13:51:18.609,fix(Toggle): Allows Figma component 'Label' text override persistence between 'top' and 'left' variants.,"
-
-### Description
-
-
-
-Currently text overrides to the label don't persist between Top and Left configurations.
-
-This update changes layer names to allow overrides to persist.
-
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-
-#### Bonus
-
-This branch also updates the `toggle-disabled` variants to use `$gray-200`.
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/XizLfOwUBqVhE3X0PAbKb8/?node-id=425%3A140)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [-] **Assignee**: If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. [-] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [-] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [-] If you’re a community contributor, please consider [transfering ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [-] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [-] **Assignee**: When applicable, [create an MR in this repository][new-gitlab-ui-mr] and apply the ""component-guideline"" template
- to create or update the component’s documentation page. If you do not have capacity, [create an issue in this repository using the ""Component documentation"" issue template][pajamas-component-documentation-template]. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [ ] **Assignee**: When applicable, [create an issue in GitLab UI using the ""Component"" issue template][gitlab-ui-component-template] to build or update the component code. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[pajamas-component-documentation-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-[new-gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new",1
-102772320,2022-02-21 08:01:46.106,"Update Figma file permissions to ""Anyone with link can view""","## Problem
-
-Figma links in the Pajamas component docs are set to `Anyone at GitLab can view` permissions. It means that those outside of GitLab can't view the Figma files that we link to from the Pajamas docs.
-
-It was discovered in [this MR thread.](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2719#note_838072427)
-
-## Proposal
-
-Update the Figma file permissions to be `Anyone with a link can view`.",1
-102039893,2022-02-08 08:08:35.935,Provide guidelines for the usage of Drawers for consistent presentation of in-product Help information,"### Description
-
-Among other things, Drawers are used to present in-product contextual help information in GitLab. We need to provide guidelines for the usage of Drawers for Help information specifically to ensure consistent experience and a certain standard for the formatting and presentation of help info.
-
-#### Questions to consider
-
-* What are the nuances of using a Drawer for Help information? How can we standardize the design of Help drawers in GitLab?
-* What kind of content does / does not belong in the drawer?
-* What is the order of types of content?
-* Where does the content reside for best updating? Right now, it is hardcoded in the product.
-* Requirement for TW to be involved in the Help window content creation (this type of content shouldn't extensively duplicate what is already available (potentially - need to think about this one); should not consist of mostly links; should answer very specific targeted questions, should follow our CTRT design guidelines). For example - the types of content in the CI/CD example are concept, task, tip, reference. Great content and the order is helpful.
-
-
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] Assign the correct component label to this issue.
-1. [x] Create an MR with the additions or updates needed.
-1. [ ] When applicable, [create a new Pajamas issue using the ""Figma update"" issue template][pajamas-figma-update-template] to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a new GitLab UI issue using the ""Component""][gitlab-ui-component-template] issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",3
-102039696,2022-02-08 08:02:35.219,Clarify drawer usage guidelines,"### Description
-
-This issue is to clarify several questions about the [Drawer component](https://design.gitlab.com/components/drawer/) usage guidelines as surfaced in [this audit. ](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/376#note_750204850)
-
-#### Questions to answer
-
-* Should we allow the drawer size to be changed?
-* Should the drawer have white or gray background? We have both instances in the product.
-* If drawer has a scrollbar, should the width be increased or the usable content area decreased? [Context](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73955)
-* Do drawers have a ""collapsed but still slightly visible"" state? (like our right/left sidebars currently do). Or are they fully visible / fully hidden?
-* Can drawers be on the left? Should our sidebars be flipped in RTL layouts (these are more broadly very broken)
-* Can drawers be stacked (and overlap slightly)? Or there can be only one at a time. [Context](https://gitlab.com/gitlab-org/gitlab/-/issues/338718#note_752946251)
-
-
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] Assign the correct component label to this issue.
-1. [x] Create an MR with the additions or updates needed.
-1. [-] When applicable, [create a new Pajamas issue using the ""Figma update"" issue template][pajamas-figma-update-template] to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [x] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a new GitLab UI issue using the ""Component""][gitlab-ui-component-template] issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [x] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",2
-102008238,2022-02-07 16:00:31.584,Pajamas UI Kit > Form component updates,"## Purpose
-
-Make updates to the way form components are constructed in the UI kit to reduce the number of component variants. [View the inspiration →](https://www.youtube.com/watch?v=9w0sOpsS90s)
-
-Figma branch [#1235-form-exploration-JE →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/ubxFCR4pADM7ZfMJ7ZvyOU/Component-library?node-id=3050%3A0)",3
-101895697,2022-02-04 15:29:10.292,Add New Popover with Close Button Variant to Pajamas,"
-
-### Description
-
-As per https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/2630, we are introducing a close option to our popover component. We need to add it to Figma.
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/mSByfa79OJuwmTqQXudJhB/Component-library?node-id=425%3A131)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [ ] **Assignee**: If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, please consider [transfering ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] **Assignee**: When applicable, [create an MR in this repository][new-gitlab-ui-mr] and apply the ""component-guideline"" template
- to create or update the component’s documentation page. If you do not have capacity, [create an issue in this repository using the ""Component documentation"" issue template][pajamas-component-documentation-template]. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: When applicable, [create an issue in GitLab UI using the ""Component"" issue template][gitlab-ui-component-template] to build or update the component code. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[pajamas-component-documentation-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-[new-gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new",1
-101844299,2022-02-03 19:07:37.244,Add browser settings to keyboard audit,"## Purpose
-
-In https://gitlab.com/gitlab-org/gitlab/-/issues/349787#note_828606021 browser settings were brought up that enable all focusable items to receive focus. This MR adds a note about it to https://design.gitlab.com/accessibility-audits/keyboard-only.",1
-101690996,2022-02-01 23:11:50.007,Alert > Allow fluid layout to determine width,"## Purpose
-
-In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/79235 it was determined that we should remove the max-width for alert content when the user's layout preference is set to fluid. This issue will update the documentation to remove that requirement.",1
-101399064,2022-01-27 15:41:24.022,Feature idea: Pattern builder,,3
-101274857,2022-01-26 10:06:27.089,Popover > Document close button usage,"### Description
-
-
-
-As per https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/2630, we are introducing a close option to our popover component. We need to document its usage.
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] Assign the correct component label to this issue.
-1. [x] Create an MR with the additions or updates needed.
-1. [x] When applicable, [create a new Pajamas issue using the ""Figma update"" issue template][pajamas-figma-update-template] to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [x] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a new GitLab UI issue using the ""Component""][gitlab-ui-component-template] issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",1
-101227845,2022-01-25 15:12:14.168,Empty search results vs empty filter results empty state text guidance,"### Description
-
-We added some documentation around empty search results recently in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1210. When I used them for https://gitlab.com/gitlab-org/gitlab/-/issues/339525/designs/Deleted-many-items.png#note_820337312, they didn't quite fit since there were filters applied. There are cases when something is searched within a search input field that will result in no matches, as well as when something is filtered within the filter component that can also result in no matches. We should decide whether or not we want to provide different messaging for those.
-
-
-
-### Audit of empty state cases
-
-| Summary |
-| ------ |
-| Whether we use a search component to filter down results, or the filter component, we do not consistently provide messages as to why there were no matches. |
-
-👉 When using the filter component, `7/17` instances use something similar to the following text:
-
-**Sorry, your filter produced no results**
-
-To widen your search, change or remove filters above
-
-👉 When using the search component, `only 3/10` instances use something similar to the following text:
-
-**Sorry, no projects matched your search**
-
-Full audit table
-
-| Search input field | Filters |
-| ------ | ------ |
-| Projects  | Issues  |
-| Groups  | Members  |
-| Explore topics  | Requirements  |
-| Milestones  | Merge requests  |
-| Projects sub-menu  | Pipelines  |
-| Global search  | Global search with filters  |
-|Labels  | Test cases  |
-|Commits  | Vulnerability report  |
-|Branches  | Policies  |
-|Tags  | Incidents  |
-|cell | Package registry  |
-|cell | Container registry  |
-|cell | Value stream analytics  |
-|cell | Code review  |
-|cell | Issue analytics  |
-|cell | Merge Request Analytics  |
-|cell | To-Do List  |
-
-
-
-### Proposal
-
-#### Search
-
-If a page uses the [search component](https://design.gitlab.com/components/search), use the following text for empty states:
-
-**No results found**
-
-Edit your search and try again.
-
-#### Filter
-
-If a page uses the [filter component](https://design.gitlab.com/components/filter), use the following text for empty states:
-
-**No results found**
-
-Edit your filters and try again.
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] Assign the correct component label to this issue.
-1. [x] Create an MR with the additions or updates needed. https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2751
-1. [ ] When applicable, [create a new Pajamas issue using the ""Figma update"" issue template][pajamas-figma-update-template] to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a new GitLab UI issue using the ""Component""][gitlab-ui-component-template] issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",1
-101219535,2022-01-25 14:04:42.470,Update Pajamas with information about the new iconography,"### Description
-
-
-
-Updates to https://design.gitlab.com/product-foundations/iconography based on the work done https://about.gitlab.com/blog/2021/12/17/hey-icons-lighten-up/
-
-As a designer trying to onboard I had to rely on external sources (and my memory) to read this section of the design system.
-
-Related to #1202.
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] Assign the correct component label to this issue.
-1. [x] Create an MR with the additions or updates needed.
-1. [ ] When applicable, [create a new Pajamas issue using the ""Figma update"" issue template][pajamas-figma-update-template] to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a new GitLab UI issue using the ""Component""][gitlab-ui-component-template] issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",3
-100940753,2022-01-19 21:57:24.167,UI kit > Update checkbox and radio components,"## Purpose
-
-- Update components to make better use of variants.
-- Add indeterminate (checkboxes only and disabled states.
-
-### Reference
-
-There's an [existing Figma branch](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/zuwBQHtdwn2KALwuKRuvvB/Component-library), but it's a bit far behind the main and there are some other approaches to explore so a new branch is preferred.
-
-Here's an example of what's there though:
-
-| **Checkbox** | **Radio** |
-| ------ | ------ |
-|  |  |",2
-100450014,2022-01-11 18:37:05.300,Text guidance for blank state,"We don't have consistent text in our blank state pages in the UI. We need to create guidance and apply it.
-
-Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/339525/designs/Deleted-many-items.png#note_807219530
-
-If you look at the following examples, the most effective ones have a call to action.
-
-Should there be different text, based on the type of page? For example, does it make sense to have a call to action on a search or filter page that shows no results?
-
-## Current guidance
-
-I found this info in Pajamas:
-
-* https://design.gitlab.com/regions/empty-states
-* https://design.gitlab.com/regions/empty-states#blank-content
-
-And there is an empty state template: https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Empty%20state
-
-It does define different types of blank state pages:
-
-- Blank page with a call to action
-- Configuration required
-- Higher tier required
-- Empty search results
-
-We should recommend text for each.
-
-## Examples of empty state pages
-
-The following are just random examples from the UI.
-
-### Package Registry
-
-https://gitlab.com/sselhorn/test-project/-/packages
-
-
-
-### Pipelines
-
-https://gitlab.com/gitlab-org/gitlab/-/pipelines?page=1&scope=finished&username=gdoyle
-
-
-
-### Merge requests
-
-https://gitlab.com/dashboard/merge_requests?scope=all&state=opened&assignee_username=hmjang1
-
-
-
-### Issues
-
-https://gitlab.com/gitlab-org/gitlab/-/issues?search=adkfhasidhf&sort=created_date&state=opened
-
-
-
-### Container Registry
-
-
-
-### Infrastructure Registry
-
-
-
-### Monitor > Metrics
-
-
-
-### Monitor > Tracing
-
-
-
-### Monitor > Incidents
-
-
-
-### Security & Compliance > Security Dashboard
-
-
-
-### Commit search
-
-https://gitlab.com/gitlab-org/gitlab/-/commits/master?search=gdgdfg
-
-
-
-### Repository > Locked files
-
-
-
-### Issues > Milestones
-
-https://gitlab.com/sselhorn/test-project/-/milestones
-
-
-
-### Issues > Requirements
-
-
-
-### CI/CD > Schedules
-
-
-
-### CI/CD > Test cases
-
-
-
-### Deployments > Feature flags
-
-
-
-### Infrastructure > Serverless platform
-
-",2
-99922200,2021-12-30 13:57:34.199,Pajamas UI Kit > Add optional prop to form label,"## Purpose
-
-Form labels can have ""(optional)"" appended to them. It uses a different text style and would be useful to include as an option in Figma similar to how it is in GitLab UI. The text remains editable.
-
-Toggling the optional property in GitLab UI:
-
-
-
-[View the branch in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/QfyaK2zgr2FFlwtDKrdHQy/Component-library?node-id=425%3A10)
-
-Here's a quick video demo:
-
-
-
-**Note**: This implementation doesn't account for text wrapping. If the label happened to be too long then you can either consider a shorter label, or detach the instance to format it in a design comp.",1
-99190879,2021-12-16 18:50:23.448,Single stat documentation,"### Description
-
-
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] Assign the correct component label to this issue.
-1. [ ] Create an MR with the additions or updates needed.
-1. [ ] When applicable, [create a new Pajamas issue using the ""Figma update"" issue template][pajamas-figma-update-template] to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a new GitLab UI issue using the ""Component""][gitlab-ui-component-template] issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",3
-98955954,2021-12-13 15:58:05.512,Migrate component examples and docs to embedded GitLab UI stories,"With https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1175 closed, we now have a way to embed GitLab UI stories in design.gitlab.com: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/embed-gitlab-ui-stories.md.
-
-The [initial implementation](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2447) migrated alerts and banners to use this new approach, but several other pages are still using legacy examples and implementation tabs. Let's migrate remaining pages, the only pre-requisite being that the corresponding GitLab UI component(s) must have been migrated to the Component Story Format (https://gitlab.com/groups/gitlab-org/-/epics/5651).
-
-## Migration steps
-
-* [ ] In the `.md` file:
- * [ ] Migrate the `vueComponents` property to `stories` in the frontmatter.
- * [ ] Migrate `[[Example:*]]` tags to `[[Story:*]]` tags.
- ```patch
- diff --git a/contents/components/accordion.md b/contents/components/accordion.md
- index 62da0f1..19fcdb2 100644
- --- a/contents/components/accordion.md
- +++ b/contents/components/accordion.md
- @@ -1,8 +1,8 @@
- ---
- name: Accordion
- description: An accordion is used to show and hide content.
- -vueComponents:
- - - GlAccordion
- +stories:
- + - base-accordion--default
- related:
- - modal
- - tree
- @@ -11,7 +11,7 @@ related:
-
- ## Examples
-
- -[[Example:accordion-basic]]
- +[[Story:base-accordion--default]]
-
- [View in Pajamas UI Kit →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Pajamas-UI-Kit?node-id=425%3A0)
-
- ```
-* [ ] Remove the associated examples from the `examples/` directory.
-
-## Migration status
-
-| Component | Can be migrated | Migrated |
-| --------------------------------------------------------------------------- | ------------------ | ------------------ |
-| [accordion](https://design.gitlab.com/components/accordion) | :white_check_mark: | :white_check_mark: |
-| [alert](https://design.gitlab.com/components/alert) | :white_check_mark: | :white_check_mark: |
-| [avatar](https://design.gitlab.com/components/avatar) | :white_check_mark: | :white_check_mark: |
-| [badge](https://design.gitlab.com/components/badge) | :white_check_mark: | :white_check_mark: |
-| [banner](https://design.gitlab.com/components/banner) | :white_check_mark: | :white_check_mark: |
-| [breadcrumb](https://design.gitlab.com/components/breadcrumb) | :white_check_mark: | :white_check_mark: |
-| [broadcast-message](https://design.gitlab.com/components/broadcast-message) | :white_check_mark: | :white_check_mark: |
-| [button](https://design.gitlab.com/components/button) | :white_check_mark: | |
-| [card](https://design.gitlab.com/components/card) | :white_check_mark: | :white_check_mark: |
-| [checkbox](https://design.gitlab.com/components/checkbox) | :white_check_mark: | :white_check_mark: |
-| [color-picker](https://design.gitlab.com/components/color-picker) | | |
-| [date-picker](https://design.gitlab.com/components/date-picker) | | |
-| [drawer](https://design.gitlab.com/components/drawer) | | |
-| [dropdown](https://design.gitlab.com/components/dropdown) | | |
-| [file-uploader](https://design.gitlab.com/components/file-uploader) | | |
-| [filter](https://design.gitlab.com/components/filter) | | |
-| [form](https://design.gitlab.com/components/form) | | |
-| [infinite-scroll](https://design.gitlab.com/components/infinite-scroll) | | |
-| [label](https://design.gitlab.com/components/label) | :white_check_mark: | :white_check_mark: |
-| [list](https://design.gitlab.com/components/list) | | |
-| [modal](https://design.gitlab.com/components/modal) | :white_check_mark: | |
-| [pagination](https://design.gitlab.com/components/pagination) | :white_check_mark: | |
-| [path](https://design.gitlab.com/components/path) | :white_check_mark: | :white_check_mark: |
-| [popover](https://design.gitlab.com/components/popover) | | :white_check_mark: |
-| [progress-bar](https://design.gitlab.com/components/progress-bar) | :white_check_mark: | :white_check_mark: |
-| [radio-button](https://design.gitlab.com/components/radio-button) | :white_check_mark: | |
-| [search](https://design.gitlab.com/components/search) | | |
-| [segmented-control](https://design.gitlab.com/components/segmented-control) | :white_check_mark: | |
-| [skeleton-loader](https://design.gitlab.com/components/skeleton-loader) | :white_check_mark: | |
-| [socks](https://design.gitlab.com/components/socks) | | |
-| [sorting](https://design.gitlab.com/components/sorting) | :white_check_mark: | |
-| [spinner](https://design.gitlab.com/components/spinner) | :white_check_mark: | |
-| [table](https://design.gitlab.com/components/table) | | :white_check_mark: |
-| [tabs](https://design.gitlab.com/components/tabs) | | |
-| [toast](https://design.gitlab.com/components/toast) | | |
-| [toggle](https://design.gitlab.com/components/toggle) | :white_check_mark: | :white_check_mark: |
-| [token](https://design.gitlab.com/components/token) | :white_check_mark: | :white_check_mark: |
-| [tooltip](https://design.gitlab.com/components/tooltip) | :white_check_mark: | |
-| [tree](https://design.gitlab.com/components/tree) | | |
-| [empty-states](https://design.gitlab.com/regions/empty-states) | :white_check_mark: | :white_check_mark: |",3
-98849054,2021-12-10 18:27:17.578,UI kit > Update components to light icons,"## Purpose
-
-With https://gitlab.com/gitlab-org/gitlab-svgs/-/issues/178 getting implemented in https://gitlab.com/gitlab-org/gitlab-svgs/-/merge_requests/739 we can update the icons in the Pajamas UI Kit.
-
-The new icons will be maintained in a separate file from the component library for easier maintenance and sharing.
-
-**Steps**
-
-1. [x] Ensure all icons that weren't updated in the recent effort, but are still part of the library, are included in the new icon file. For example, pipeline, issue type, and brand icons.
-1. [x] Publish the new icon library and add it to our community page.
-1. [x] Replace the icons in the component library with the ones from the new icon library.
-1. [x] Deprecate the old icons by removing them from the component library and placing into a separate file that will be archived.
-1. [x] Publish an updated version of the component library.
-1. [x] Mention the breaking change in the UX Weekly with directions on using the new library.
-1. [x] Create a new MR to update the iconography guidelines in Pajamas.",2
-98765575,2021-12-09 16:42:44.763,Illustration > Add more grid information,"## Purpose
-
-In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2636 the product illustration guidelines were updated. Based on some feedback there could be more helpful guides specifically around the grid.
-
-> A link to some resource would be helpful, or at least some examples of illustrations within this grid so it's easier to see what are the focal points and how elements should align to it. https://design.gitlab.com/product-foundations/illustration#focal-point-grid
->
-> This grid is specific to illustration, so I wouldn't assume all Product Designers know how to use it if they haven't had experience with graphic design or illustration.",1
-98752241,2021-12-09 13:29:08.659,UI kit > Define & validate shadow style specs,"## Problem
-
-The current layer shadow style/specs in the UI kit ([modal example](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=4263%3A22)) don't align with what's in [Pajamas](https://design.gitlab.com/layout/layers#large). This issue is to determine the correct specs and where updates are needed.
-
-[View branch in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/k1Qah0jN5geit4umN5uCYI/Component-library)
-
-| **UI kit** (Note that both are combined into one shadow) | **Pajamas** |
-| ------ | ------ |
-|  | ```box-shadow: 0px 0px 4px rgba(0, 0, 0, 0.16), 0px 4px 12px rgba(0, 0, 0, 0.16);``` |
-
-## Solution
-
-Consolidated list of styles based on components in production and in the UI kit
-
-## Shadow styles
-
-### Small shadow - {+new+}
-
-| GitLab-ui | GitLab UI kit | Components | CSS |
-| ------ | ------ | ------ | ------ |
-| $gl-shadow-sm | Small $gl-shadow-sm | Card | `box-shadow: 0px 1px 2px rgba(0, 0, 0, 0.1);` |
-
-### Medium shadow - {+new+}
-
-| GitLab-ui | GitLab UI kit | Components | CSS |
-| ------ | ------ | ------ | ------ |
-| $gl-shadow-md | Medium $gl-shadow-md | Date picker, Dropdown, Menus, Flyout Nav, Card `on_drag` | `box-shadow: 0px 2px 8px rgba(0, 0, 0, 0.16), 0px 0px 2px rgba(0, 0, 0, 0.16);` |
-
-### Large shadow
-
-| GitLab-ui | GitLab UI kit | Components | CSS |
-| ------ | ------ | ------ | ------ |
-| $gl-shadow-lg | Large $gl-shadow-lg | Modal, Drawer | `box-shadow: 0px 4px 12px rgba(0, 0, 0, 0.16), 0px 0px 4px rgba(0, 0, 0, 0.16);` |
-
-
-
-## Changes for this issue
-
-### UI Kit
-
-- [x] Add missing shadow layer styles (sm & md)
-- [x] Update the shadow-sm to be more appropriate for the card on boards.
-
-### Pajamas
-
-- [ ] Update documentation to reflect new styles
-- [ ] Update images to follow `visual example` patterns
-
-## GitLab UI
-
-### In https://gitlab.com/gitlab-org/gitlab-ui/-/issues/615
-
-1. Document new shadow styles and audit existing styles
-1. Add new shadow styles as utility classes
-1. Update instances to use the new GitLab UI utility classes
-
-```
-Out of scope but worth mentioning;
-
-* gl-shadow-focus: focus states
-
-This will remain unchanged in Gitlab-UI
-```",1
-98706269,2021-12-08 20:56:53.115,Bug: 404 when opening a component page directly to the /contribute tab,"To recreate:
-
-Click this link: https://design.gitlab.com/components/table/contribute",3
-98703259,2021-12-08 19:21:00.631,"Follow-up from ""feat(Illustration): Update docs with new guides""","The following discussion from !2636 should be addressed:
-
-- [x] @tauriedavis started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2636#note_757943934): (+4 comments)
-
- > **non-blocking:** The figma frame has a purple background which is a bit odd. Can that be updated to be like the one above where it's on the toggle? :thinking:",1
-98620537,2021-12-07 17:46:35.492,Inline note layout broken,"## Problem
-
-Recently we updated the look of the inline todo, but the change has also been applied to the inline note, which has different design constraints.
-
-| **Todo** | **Note** |
-| ------ | ------ |
-|  |  |
-
-## Solution
-
-Use a different layout for an inline note. Ideally the note content could have normal vertical flow to support longer content.",2
-98611089,2021-12-07 14:51:50.639,chore: Organize img folder,,1
-97030215,2021-11-09 17:17:24.992,Update todo note style,"## Purpose
-
-Update the todo styles to be more streamlined.
-
-- Take up less vertical space and overall reduce visual weight.
-- Allow the ""Create an issue"" link to stand out.
-- Use a simple document (note) icon to insinuate that this is a note.
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-
-[View in Figma →](https://www.figma.com/file/0enu1LVbrKOuhTjLsbRsb0/%231182-todo-update?node-id=0%3A1)",1
-96281477,2021-10-27 20:23:12.555,Live example SSoT,"From a Foundations Open Office Hours agenda:
-
->Correct me if I’m wrong, but we still have to update Pajamas examples to match GitLab UI stories, right? As I’ve been working through the accessibility audits, my assumption is that any change to the component in GitLab UI will mean that updates have to happen in Pajamas too. Any ideas on being able to have one live example SSoT?
-
-Generally at the moment I think just about everything could be affected since one version exists in Storybook in either example or CSF format, and there'd be an example in Pajamas.
-
-Recent example since I was working on auditing breadcrumbs. The separator isn't the same…
-
-| **GLUI** | **PJs** |
-| ------ | ------ |
-|  |  |
-
-Tabs was even more confusing because there are both stories and examples in GitLab UI, and then examples in Pajamas. I've worked on aligning them, but changes had to be made in all three places.
-
-Another hypothetical example might be where we update the markup in a modal CSF, but then have to update in Pajamas example to match.",3
-96127181,2021-10-26 02:55:24.941,Illustration > Update docs with new guides,"After https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1087 there should be sweeping changes to the [Illustration](https://design.gitlab.com/product-foundations/illustration) documentation to outline the new process and guidelines.
-
-## Process
-
-* [x] Update https://design.gitlab.com/product-foundations/illustration.
-* [x] Ensure that related issue templates and project docs are current.
-* [x] Communicate changes to the UX team.",3
-95823882,2021-10-20 21:08:59.181,Figma > Update Figma for GitLab guide,"With Figma updates and new features and workflows to leverage, it's time to update the [**Figma for GitLab**](https://www.figma.com/file/73OcYdBfOaK2xlChC3tbNX/Figma-for-GitLab?node-id=0%3A1) deck.
-
-[View the WIP branch →](url)",2
-95815719,2021-10-20 17:49:21.832,Update Figma issue template,"This is related to the effort in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1130, and ensuring that the issue template also contains accurate, up-to-date information about Figma and our process.",1
-95803680,2021-10-20 14:43:53.580,Update contribution resources to account for Objects,"Update contributor guidelines, MR templates, component lifecycle, and others…
-
-1. [x] https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2726 and https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2744 — Update [MR template](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md) to be generic for any kind of documentation update, including objects, and update its links.
-1. [x] https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2727 — Expand on [object overview](https://design.gitlab.com/objects/overview) page, moving generic content out from the individual object pages.
-1. [x] [Figma branch (merged)](https://www.figma.com/file/J68bePHXIN5OPWqaFFY9ri/branch/5tlA0Ov1H7coIxFqihWytc/Conceptual-model?node-id=5823%3A553) — Add example page and legend to conceptual model file with stickies explaining components (object and lines). Add legend component to each object page in Figma.
-1. [x] https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2769 — Embed [conceptual model example page](https://www.figma.com/file/J68bePHXIN5OPWqaFFY9ri/?node-id=5823%3A553) in the [objects overview page](https://design.gitlab.com/objects/overview/).",1
-95803660,2021-10-20 14:43:23.983,Review and polish Figma conceptual model file for Objects,"[🖼 Main Figma file](https://www.figma.com/file/J68bePHXIN5OPWqaFFY9ri/Conceptual-model)
-
-- [x] Convert file cover to standard Pajamas cover
-- [x] Add objects “folder” page
-- [x] Add icons to help identify pages
-- [x] Add Pajamas link at the top of each published object
-- [x] [Create variants for object and line components](https://www.figma.com/file/J68bePHXIN5OPWqaFFY9ri/branch/qCgSr8rBqgrm0TCTuwCo4T/Conceptual-model)",2
-95367381,2021-10-13 14:55:21.703,Breadcrumb > Update example to use the GitLab UI story,Use the GitLab UI story as the SSoT for the embedded example.,1
-95286769,2021-10-12 14:04:31.834,Badge > Update accessibility guides,"## Purpose
-
-I created a quick Codepen test https://codepen.io/lostsatellites/pen/WNEezQd to validate how a badge is announced in context. Because it's a piece of metadata it likely won't make sense on its own, so these additional considerations take that into account.",1
-95123649,2021-10-08 17:15:30.673,Add skip link to Pajamas site,"## Purpose
-
-The Pajamas website doesn't have a skip link to jump keyboard users to the main content area. This adds one so that as the first focusable item a keyboard user can have focus moved to `main`. This will also aid in being able to access in-page rendered examples quicker instead of tabbing through all of the navigation.
-
-The pattern outlined in https://css-tricks.com/a-deep-dive-on-skipping-to-content/ will be the starting point.",1
-95106896,2021-10-08 12:16:48.525,Create an Object issue template,"## 🧩 Problem
-
-We've started documenting objects in Pajamas (see the [MR object](https://design.gitlab.com/objects/merge-request)). Currently we don't have any contribution guidelines for documenting objects. For someone unfamiliar with the purpose and process of object modeling it can be intimidating and difficult to get started.
-
-The conceptual object model becomes more useful as more objects and layouts are documented since it helps communicate the relationships between different objects. The more objects and layouts we document (even if the model is imperfect at first), the more we'll be able to use it. For example, it can help identify important object relationships and ensure we don't overlook them in our design work.
-
-## 💡 Proposal
-
-We don't need to create a perfect set of guidelines and templates to start benefiting from the documented model. The objective is to create an MVC set of guidelines and resources to get more product designers interested in contributing.
-
-This issue will focus on adding an Object issue template to guide designers as they document the conceptual model and the layouts for the object.",2
-94525527,2021-09-29 10:36:14.286,Date picker - make month/year look more interactive,"# Problem
-
-- The date picker has a dropdown for the month and year and nobody knows about it!
-- Related to #601. From this thread: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/601#note_689319507
-
-# Proposal
-
-- Use a similar pattern to the sidebar - with a tertiary button that goes to `gray-50` on-hover to show interaction...
-
-
-
-# Other ideas
-
-",1
-94403493,2021-09-27 19:34:29.155,Triage Build job failure,"## Purpose
-
-I've noticed that the **Build** job is failing for pipelines in the Pajamas project. This issue is to determine a fix.",1
-94391827,2021-09-27 15:44:40.016,UI Kit > Migrate Drawer component from Sketch to Figma,"
-
-### Description
-
-
-
-In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/376#note_683270630 it was identified that the Drawer component design specs exist in Sketch, but need to be added as a component in Figma.
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/5etp1G6sZS5O57yXQ4mxeY/Migrate-Drawer-component-from-Sketch-to-Figma?node-id=1%3A70)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [x] **Assignee**: Move your working file to the shared Figma project:
- 1. [x] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [-] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [-] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [-] **Assignee**: When applicable, [create an MR in this repository][new-gitlab-ui-mr] and apply the ""component-guideline"" template
- to create or update the component’s documentation page. If you do not have capacity, [create an issue in this repository using the ""Component documentation"" issue template][pajamas-component-documentation-template]. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [-] **Assignee**: When applicable, [create an issue in GitLab UI using the ""Component"" issue template][gitlab-ui-component-template] to build or update the component code. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[pajamas-component-documentation-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-[new-gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new",2
-94158909,2021-09-23 03:54:01.459,"Follow-up from ""feat(Drawer): Update content to utilize new template""","The following discussion from !2546 should be addressed:
-
-- [x] @tauriedavis started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2546#note_684885183): (+1 comment)
-
- > - If supplemental content isn't suited for small areas or is part of a flow, consider loading a new page, revealing content with an [accordion](/components/accordion), or using a [modal](/components/modal) instead.
- >
- >> I'm hesitant to add modal here as an option for when supplemental content isn't suited for small areas. I wonder if there is additional info to add here about where a modal should be used in place of a drawer (such as the line below this one).",1
-93885645,2021-09-17 20:36:40.957,Update Pajamas UI Kit contribution guidelines,"## Purpose
-
-As new features have been released in Figma, so too we've started using them and changed up a few workflows. The [**Pajamas UI Kit contribution and updating guidelines**](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components) document could use a thorough review along with updates.
-
-/cc @mle @lvanc @nadia_sotnikova @cam.x @tauriedavis",2
-93667422,2021-09-14 19:01:09.978,Pajamas UI Kit > Text input add-on component variable,"## Purpose
-
-Recently the [text input base](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=43905%3A45856) was updated to include prefix and suffix options while the add-ons remained unchanged. This issue addresses making the add-ons easier to change and update in a similar way.
-
-
-
-## Scope
-
-Create a branch of the component library **❖ _Base Add-on** component with the following variants:
-
-- Character count
-- Clear button ([clear](https://gitlab-org.gitlab.io/gitlab-svgs/?q=~clear) icon) to clear entered content
-- Show button ([eye](https://gitlab-org.gitlab.io/gitlab-svgs/?q=~eye) icon) for password visibility
-- Hide button ([eye-slash](https://gitlab-org.gitlab.io/gitlab-svgs/?q=~eye-slash)) for obscuring password
-- Calendar button ([calendar](https://gitlab-org.gitlab.io/gitlab-svgs/?q=~calendar) icon) for date picker
-
-The character count can be present with the buttons, but only one button can be visible at a time.
-
-**Additional changes:**
-
-- The add-ons in the **❖ _Base Field** component will be replaced with the **❖ _Base Add-on** component.
-- Currently the add-ons are set to true/false for the **Text input** component and will need to be changed to a dropdown to choose the type of add-on. The **Text area** component can remain as true/false as long as the character count is the only option.
-- All component variants will need to be updated to look the same as they do today, only they will have the correct add-on chosen by default. This applies to everything in **Forms**, as well as **Datepicker** and **Dropdown**.
-
-### Design file
-
-Figma: https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/5BKoo354GwPXInx3EsPDFa/Component-library?node-id=425%3A10 `1120-working-branch-veethikaa`",3
-93648529,2021-09-14 14:32:11.383,Component template: Component structure image,"This issue is to discuss adding multiple structure images and what state the component should be in for the structure image. Based on https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2520#note_671632056.
-
-Two main questions:
-
-1. What state of the component should be the structure image? For example:
-
-| Beginning | All possible elements (Base component) |
-| ------ | ------ |
-|  |  |
-
-Which should be the structure image? My assumption is to use the base component so we can describe each possible visible element.
-
-2. Should we include multiple structure images if there are different variants? For example:
-
-| Single file uploader | Multi file uploader |
-| ------ | ------ |
-|  |  |
-
-Again, my assumption is we include both, with unique lists for each. Thoughts?",1
-93328872,2021-09-08 13:06:31.718,Frontmatter description doesn't render unless there are tabs,"Currently, we are rendering `description:` at the top of the page, but **only** if the pages contains tabs. This description should always render, regardless of whether there are tabs or not. A lot of pages don't contain tabs, so we'll never be able to utilize the `description:` unless there is a vueComponent associated with that component.
-
-For example, we are creating an overview page that utilizes the `description:` item: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1105. We are also updating the docs pages to utilize a new doc template, which utilizes the `description:` item, so if the components without a Vue component get updated to the new template, those updates will be blocked until this is resolved.",2
-93192659,2021-09-06 13:21:58.605,Pajamas UI Kit > Update top nav Figma component,"
-
-### Description
-
-
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/PVS2W2D3IioRPYvwdGmlvb/Component-library?node-id=7580%3A42) `update-consolidated-top-nav`
-
-### Screenshots
-
-Variants
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-Project menu
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [x] **Assignee**: Move your working file to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] **Assignee**: When applicable, [create an MR in this repository][new-gitlab-ui-mr] and apply the ""component-guideline"" template
- to create or update the component’s documentation page. If you do not have capacity, [create an issue in this repository using the ""Component documentation"" issue template][pajamas-component-documentation-template]. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [ ] **Assignee**: When applicable, [create an issue in GitLab UI using the ""Component"" issue template][gitlab-ui-component-template] to build or update the component code. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[pajamas-component-documentation-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-[new-gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new",3
-92292719,2021-08-19 19:30:37.860,Avatar > Reverse stack order,"## Problem
-
-The current stacked order of avatars places the last item at the very bottom. Since this can be an interactive badge I think the order should be reversed. Also, the stacking order infers who was added when. If someone was added later, it makes sense that their avatar is set on top of the one before.
-
-## Solution
-
-Continue to order the avatars from left to right, but as they're ordered from left to right, they should stack from bottom to top. This allows the badge (if present) to be the most visible item and have the largest click target when interactive.
-
-When DOM order and z-index is considered I believe this is a more natural presentation too.
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-
-[View proposal in Figma →](https://www.figma.com/file/hO6UAuOrF5Ca8ltX4rZUb9/Avatar-stack-order?node-id=2%3A844) (Note: this was a separate file and not a branch because it's only changing instances and not a component or styles.)",1
-92063977,2021-08-16 19:17:26.917,Focus ring: Explore increasing contrast,"## Purpose
-
-As a result of the audit in the parent epic, the focus ring visual styles should be reviewed to consider the following:
-
-- Increase focus ring contrast to at least 3:1 (currently 1.97:1).
-- While I believe that there is no current failure because for [SC 2.4.7](https://www.w3.org/TR/WCAG21/#focus-visible) there is a visible focus ring, and for [SC 1.4.11](https://www.w3.org/TR/WCAG21/#non-text-contrast) the button text and/or icon has sufficient contrast, there are potential updates per the [WCAG 2.2 Working Draft](https://www.w3.org/TR/WCAG22/) that we could aim to satisfy now.
- - [Success Criterion 2.4.11 Focus Appearance (Minimum)](https://www.w3.org/TR/WCAG22/#focus-appearance-minimum)
-
-**Watch recordings of the audit** (internal)
-
-[▶︎ Visual scan](https://drive.google.com/file/d/1qCB9-KfC1p-D7ao0QiwzQQMehERZZvUS/view?usp=sharing)
-
-**Current contrast:**
-
-
-
-(Contrast with opacity checked with [contrast-ratio.com](https://contrast-ratio.com/#rgb%2831%20117%20203%20%2F%2048%25%29-on-white).
-
-## Resources
-
-- https://www.sarasoueidan.com/blog/focus-indicators/
-- https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance-minimum.html",2
-91809050,2021-08-11 12:09:41.126,Elevate contribution to a tab,"How can we increase and invite contribution to Pajamas in a ""boring solution"" kind of way?
-
-Inspired by the **Discussion** tab in https://designsystem.gov.au/components/buttons/discussion/ (thanks @mle for tweeting about this site, it's awesome) I'm exploring a **Contribute** tab.
-
-What would go in there?
-
-- A bit of a text preamble with a link to the **Getting started > Contribute** page.
-- We already have links in the footer to related issues and merge requests. It'd be worth repeating here when either are available.
-- Occasional links to research efforts, polls, questionnaires, hackathons, etc. It'd be great to have some passive, evergreen items like that where someone could provide feedback.
-
-What does this solve?
-
-- Reenforcing that ""everyone can contribute,"" while creating more visibility on how.
-- What I especially liked about the Australian Government Design System example is how I felt invited into the conversation. It wasn't just one-way information. It also felt very transparent to reference discussion happening behind the scenes that you might normally not be privy to.
-
-",2
-91748971,2021-08-10 13:29:02.265,feat(markdown): Underline links in body content,"## Purpose
-
-At the moment, links in the markdown content are not underlined and have low contrast next to static text. This makes it more difficult to discern a link from surrounding text.
-
-## Solution
-
-A boring solution is simply to leverage the default `text-decoration: underline` for links within markdown. This is also proposed as an update to markdown in GitLab UI https://gitlab.com/gitlab-org/gitlab-ui/-/issues/1084, but this solution covers the gap until that is updated and Pajamas is using the markdown styles in documentation.",1
-91501194,2021-08-05 13:01:45.577,Pajamas > Add Google Analytics,"## Purpose
-
-It'd be great to have a high-level understanding of most accessed content in Pajamas and the path users take to get there.
-
-## Solution
-
-In https://gitlab.com/gitlab-com/marketing/inbound-marketing/seo/-/issues/129 we were given the ability to add Google Analytics to Pajamas.",3
-91275541,2021-08-02 13:27:31.147,FY22-Q3 KR3: Illustrate empty states for Access Tokens and Admin/Applications using new styles and assets,"Use the new style library and assets to create illustrations for the following empty states:
-
-- [x] https://gitlab.com/gitlab-org/gitlab-svgs/-/issues/196
-- [x] https://gitlab.com/gitlab-org/gitlab-svgs/-/issues/195",2
-91275453,2021-08-02 13:26:01.826,FY22-Q3 KR2: Create new illustration asset and style library,"Create a new Figma file and build a foundation of styles and assets in alignment with brand illustrations that can be used to update documentation and support a redesign of product illustration.
-
-Light and dark UI will be considered to determine if there's an efficient way to create illustrations that can also adapt to UI preference.
-
-* [x] Create a new Figma file with library styles that consider light and dark UI ~~(with mapping between the two)~~.
-* [x] Start creating reusable assets as components based on the audit in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1086 and the resources created by the brand team. ~~Initial focus specifically on assets that will support https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1088.~~
-* [x] ~~Create a POC to test CSS vars and classes within the illustrations that update based on light/dark UI settings.~~ Create a POC to test browser support for SVG with transparency and gauge the result on light/dark UI.",5
-91275385,2021-08-02 13:25:00.072,FY22-Q3 KR1: Audit current empty state illustrations,"Audit all empty state illustrations to determine what elements are repeatable and where there are opportunities to empower designers to create their own unique empty state illustrations that are based on a library of reusable assets.
-
-* [x] Audit all empty states in https://gitlab-org.gitlab.io/gitlab-svgs/illustrations (can also be referenced from Figma in https://www.figma.com/file/0DhXXlTakscLiHZLKuiJ6C/Illustration-library).
-* [x] Create a list of repeating themes, sizes, and elements that could be leveraged to create an illustration library.
-
----
-
-## Proposed state
-
-* Use a common grid to layout the illustration — one for large and one for medium (no small identified as empty states in the current illustration library).
-* Have a consistent focal-point. Leverage the grid and some keylines to help with object placement.
-* Use a consistent color palette for the focal-point element(s).
-* Establish guides on when to create a more custom illustration, and when to leverage something that's multi-purpose or more generic. For example, a more custom illustration could be created with a combination of new and existing assets for a new feature or one that isn't enabled, while an empty data state or configuration needed could always use the same asset.
-
-### Repeating themes
-
-- New feature
-- Upgrade
-- Not configured
-- No data
-
-## Sizes
-
-- Large
-- Medium
-- Small (new)
-
-## Elements
-
-* Ellipses to contain icons or graphics.
-* Dashed connectors to establish relationships.
-* Shapes to represent placeholder content.
-* Small reusable illustrations. For example, to consistently represent no data or needs configuration.
-* More TBD after starting to build this out.",3
-91023231,2021-07-28 13:20:24.385,GFM Typescale > Audio > design,"## Task
-Create Figma specs for the GitLab Flavored Markdown audio component. See parent epic for detailed information about this component.
-
-
-## [Figma branch (Audio)](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/Type-scale---Documentation-Markdown?node-id=1097%3A10)
-",1
-90925147,2021-07-27 14:17:18.646,GFM Typescale > Inline diff > design,"Create Figma specs for the GitLab Flavored Markdown inline diff component.
-
-See parent epic for detailed information about this component.
-
-Figma files:
-
-- [Documentation markdown - Inline diff](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/Type-scale---Documentation-Markdown?node-id=988%3A10)
-- [Compact markdown - Inline diff](https://www.figma.com/file/mjAZxHkK95TlQ6L14aNp2M/Type-scale---Compact-Markdown?node-id=893%3A4)",1
-90843308,2021-07-26 12:10:31.807,GFM Typescale > Code block > design,"Create Figma specs for the GitLab Flavored Markdown code block component.
-
-See parent epic for detailed information about this component.
-
-Figma assets:
-
-- [Documentation markdown - Code block](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/Type-scale---Documentation-Markdown?node-id=985%3A10)
-- [Compact markdown - Code block](https://www.figma.com/file/mjAZxHkK95TlQ6L14aNp2M/Type-scale---Compact-Markdown?node-id=890%3A8)",1
-90842445,2021-07-26 12:00:08.892,GFM Typescale > Image > design,"Create Figma specs for the GitLab Flavored Markdown image component.
-
-See parent epic for detailed information about this component.
-
-- :pencil2: [Figma branch - Documentation markdown](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/branch/gI2szSJVfByu9N0Etzucr0/Type-scale---Documentation-Markdown?node-id=974%3A10)
-- :pencil2: Figma branch - Compact markdown - TBD",1
-90744464,2021-07-23 17:18:14.582,Fix sidebar collapse when section has a collapsable sub-section,"The following discussion from !2469 should be addressed:
-
-- [ ] @jeldergl started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2469#note_633217411): (+1 comment)
-
- > @tauriedavis something seems to be broken with this extra nested level. It's always open and looks active by default, even when navigating to other pages. Closing it closes the parent too. I haven't been able to dig into this further, but it makes me wonder if something with the JS has to get updated.
- >
- > ",2
-90737033,2021-07-23 14:29:02.431,GFM Typescale > Blockquote > design,"Create Figma specs for the GitLab Flavored Markdown blockquote component.
-
-See parent epic for detailed information about this component.
-
-### Proposal
-
-| Compact (current) | Compact (New) |
-| ------ | ------ |
-|  |  |
-
-| Documentation (current) | Documentation (New) |
-| ------ | ------ |
-|  |  |
-
-
-**Summary of changes:**
-- Left border: `4px` `$gray-100`
-- Text: `$gray-700`
-- See reasons for color updates: https://gitlab.com/gitlab-org/gitlab/-/issues/231405/
-
-### Design source
-- :pencil2: [Figma - Documentation markdown](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/branch/eMkpaCMX6MS4JsZhgRB23O/Type-scale---Documentation-Markdown?node-id=1843%3A373)
-- :pencil2: [Figma - Compact markdown](https://www.figma.com/file/mjAZxHkK95TlQ6L14aNp2M/branch/ygOLNsF7gZZlJKrrOzaGlu/Type-scale---Compact-Markdown?node-id=1657%3A170)
-- :pencil2: [Figma - Component library](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=33967%3A28794)",1
-90701620,2021-07-22 22:08:24.242,GFM Typescale > Table > design,"Create Figma specs for the GitLab Flavored Markdown table component.
-
-See parent epic for detailed information about this component.
-
-- :pencil2: [Figma branch - Documentation markdown](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/branch/vO1Ef5cah3JWGlJKq9XvGw/Type-scale---Documentation-Markdown?node-id=1174%3A11)
-- :pencil2: [Figma branch - Compact markdown](https://www.figma.com/file/mjAZxHkK95TlQ6L14aNp2M/branch/F0ml9uXBQGWz0Jg5YVjY90/Type-scale---Compact-Markdown?node-id=1554%3A78)
-
-### Summary of changes
-- Removed all vertical borders
-- Removed thicker border between header and body row
-- Changed cell text color from `$gray-900` :arrow_right: `$gray-700`
-- Changed vertical text alignment from `middle` :arrow_right: `top`
-- All inner cell content for both header and body cells has a consistent padding of `8px` L/R and `12px` T/B
-- Added alternating rows by default",1
-90700782,2021-07-22 21:21:39.168,FY22-Q3 Foundations KR1.5: Identify whether there are additional empty state types that need to be added,"- [x] After reviewing the [four empty state types](https://gitlab.com/groups/gitlab-org/-/epics/6413), identify whether there are additional empty state types that need to be added
- - [x] If yes, identify problem statements to test during the validation phase",2
-90700687,2021-07-22 21:15:56.257,"FY22-Q3 Foundations KR1.4: Review ""empty search results"" empty state","Within our empty state documentation, we've identified [four types of empty states](https://design.gitlab.com/regions/empty-states#when-to-use-an-empty-state). In this issue, we will review the `empty search results` empty state.
-
-Empty search results: Display empty search results.
-
-- [x] Find 2-3 existing examples of the `empty search results` empty state in the product
-- [x] Determine if this type of empty state is a valid use case for the empty state region
-- [x] Identify areas of possible improvement by writing problem statements to test during problem validation",1
-90700665,2021-07-22 21:14:11.770,"FY22-Q3 Foundations KR1.3: Review ""error state"" empty state","Within our empty state documentation, we've identified [four types of empty states](https://design.gitlab.com/regions/empty-states#when-to-use-an-empty-state). In this issue, we will review the `error state` empty state.
-
-Error state: Convey an error state, which will depend on the nature of the error and should be used judiciously. An example of this would be a server response error, that is, 404 or 500.
-
-- [x] Find 2-3 existing examples of the `error state` empty state in the product
-- [x] Determine if this type of empty state is a valid use case for the empty state region
-- [x] Identify areas of possible improvement by writing problem statements to test during problem validation
-
-# Outcome
-
-
-We will want to remove this from empty state guidelines, as it is not a valid use case. Errors are separate and can be handled with anything from an alert to 404 to form validation",1
-90700627,2021-07-22 21:12:33.624,"FY22-Q3 Foundations KR1.2: Review ""blank content"" empty state","Within our empty state documentation, we've identified [four types of empty states](https://design.gitlab.com/regions/empty-states#when-to-use-an-empty-state). In this issue, we will review the `blank content` empty state.
-
-Blank content: Act as a placeholder for regions in the app left blank intentionally.
-
-- [x] Find 2-3 existing examples of the `blank content` empty state in the product
-- [x] Determine if this type of empty state is a valid use case for the empty state region
-- [x] Identify areas of possible improvement by writing problem statements to test during problem validation",1
-90700580,2021-07-22 21:10:07.979,"FY22-Q3 Foundations KR1.1: Review ""unused feature"" empty state","Within our empty state documentation, we've identified [four types of empty states](https://design.gitlab.com/regions/empty-states#when-to-use-an-empty-state). In this issue, we will review the `unused feature` empty state.
-
-Unused feature: Make users aware that a feature is not configured for use.
-
-- [x] Find 2-3 existing examples of the `unused feature` empty state in the product
-- [x] Determine if this type of empty state is a valid use case for the empty state region
-- [x] Identify areas of possible improvement by writing problem statements to test during problem validation
-
-Proposals:
-
-* Update category name to `Configuration required`.",1
-90700472,2021-07-22 21:03:18.123,"FY22-Q3 Foundations KR2: Perform problem validation where necessary to understand existing limitations, creating recommendations and performing solution validation to confirm assumptions","[FY22-Q3 UX Department: Foundations SubTeam OKR](https://gitlab.com/groups/gitlab-org/-/epics/6412)
-
-Objective: Improve learnability of features by researching and providing recommendations for improved empty states with a focus on user on-boarding
-
-**KR3: Perform problem validation where necessary to understand existing limitations, creating recommendations and performing solution validation to confirm assumptions**
-
-- [ ] Using the problem statements from the [first KR](https://gitlab.com/groups/gitlab-org/-/epics/6413), perform problem validation to address assumptions
-- [ ] Generate recommendations based on research
-- [ ] Perform solution validation as needed
-
-Ally: https://app.ally.io/objectives/1453437?time_period_id=135090",3
-90700269,2021-07-22 20:56:10.949,FY22-Q3 Foundations KR3: Update empty state usage guidelines/design specs using what we've learned from research,"[FY22-Q3 UX Department: Foundations SubTeam OKR](https://gitlab.com/groups/gitlab-org/-/epics/6412)
-
-Objective: Improve learnability of features by researching and providing recommendations for improved empty states with a focus on user on-boarding
-
-**KR3: Update empty state usage guidelines/design specs using what we've learned from research**
-
-- [x] Update [empty state guidelines](https://design.gitlab.com/regions/empty-states) in Pajamas
-- [ ] ~~Update design specs in the [Figma UI Kit](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Pajamas-UI-Kit)~~
-- [x] Review [existing empty state issues](https://gitlab.com/groups/gitlab-org/-/epics?scope=all&search=empty+state&state=opened) and close any that are no longer relevant
-
-Ally: https://app.ally.io/objectives/1453438?time_period_id=135090",3
-90690258,2021-07-22 15:57:42.088,Button > Explore documentation hierarchy,"## Purpose
-
-When working through some Pajamas research related to https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, I noticed that the concept of button categories and variants was confusing for users. I still mull it over from time to time too. I’m wondering if perhaps we could reconsider the hierarchy of information here to simplify it?
-
-| **Current** | **Proposed** |
-| ------ | ------ |
-| **Category:**
- Primary
- Secondary
- Tertiary
**Variants:**
- Confirm
- Default
- Dashed
- Danger
- Link | **Variants:**
- Confirm
- Primary
- Secondary
- Tertiary
- Default
- _Same pattern as Confirm_
- … |
-
-This would focus on the variants, and then the options for each variant. I think doing away with the category content as-is would be helpful. We can still identify primary, secondary, and tertiary actions, but secondary to variant. We could always take naming further, but a change like this doesn't require component changes as far as I can tell, just how it's presented.",3
-90680025,2021-07-22 12:50:23.019,GFM Typescale > Code span > design,"Create Figma specs for the GitLab Flavored Markdown code span component.
-
-See parent epic for detailed information about this component.
-
-- [Documentation markdown - Code span](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/Type-scale---Documentation-Markdown?node-id=909%3A10)
-- [Compact markdown - Code span](https://www.figma.com/file/mjAZxHkK95TlQ6L14aNp2M/Type-scale---Compact-Markdown?node-id=862%3A4)",1
-90567168,2021-07-20 15:06:53.560,Add Pajamas Playground to documentation,"### Problem
-
-While the Pajamas documentation provides extensive examples and code snippets for our components, there is currently no easy way to try our design system without installing GDK or creating a GitPod instance.
-
-### Proposal
-
-This issue proposes adding a Pajamas Playground to our documentation (potentially as a simple iframe), to remedy this gap and enable designers & developers to:
-
-- Quickly try component code directly in the browser
-- Test different component props and combinations
-- Easily collaborate and generate code snippets for other developers
-
-**Question for the Foundations Team**: Do you see this as something useful and worth integrating into the docs?
-
-You can see a working proof of concept at https://dfosco.gitlab.io/pajamas-playground
-
-
-
-### Possible Next steps
-
-The proof of concept above is a very rough prototype, and it can likely break very easily. Possible next steps to integrate this as an official part of our tooling include:
-
-- Embed playground in a dedicated page of Pajamas docs
-- Update code to dynamically import the latest version of _every_ Pajamas component (including new ones)
-- Add sharing button to append current code to URL -- see [example on Auth0 docs](https://auth0-cosmos.vercel.app/#/playground)
-- General cleanup of the code to meet team standards and reliability",2
-90357136,2021-07-15 20:55:24.985,Pajamas > Move contributing content,"## Problem
-
-- Recently the **Component lifecycle** content was updated, but it still remains the last item in the menu and could be elevated for more visibility.
-- Under the **Contribute** menu heading there is a **Get started** page, but there is already a **Get started** navigation heading above.
-
-## Solution
-
-- Move the **Component lifecycle** page under the top **Get started** menu heading.
-- Move the **Get started** page under the top **Get started** menu heading and rename the page to ""Contribute.""
-- Remove the **Contribute** menu heading.
-- Update any Pajamas links to point to the new pages.
-
-",2
-90289738,2021-07-14 19:19:57.566,Regions > Add merge request reports,"## Purpose
-
-Add [merge request reports](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=38197%3A204050) to the **Regions** section of Pajamas. The initial content will come from the [Figma file](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=38197%3A204050). This is in preparation of the implementation phase for the MR widgets and having the SSoT in Pajamas.",2
-90287401,2021-07-14 18:11:48.454,"Follow-up from ""feat(Color): Add color theme notes""","The following discussion from !2460 should be addressed:
-
-- [ ] @jeldergl started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2460#note_625218336): (+6 comments)
-
- > Note: these changes (and others like it) were brought about by the lint job that runs during a commit.
-
----
-
-The changes in question was the removal of indentation for HTML within a markdown file. The indentation helps with nesting and understanding the code. Removing it makes the markup harder to read and understand.",1
-89872209,2021-07-07 03:12:00.014,Update Sidebar navigation component,"
-
-### Description
-
-
-
-Updating the `Sidebar` component to match the direction of the navigation changes from %""14.0""
-
-- Using the gray-900 color instead of having theme color influence the sidebar https://gitlab.com/gitlab-org/gitlab/-/issues/330467
-- Using the name `Infrastructure` instead of `Kubernetes` in instances to reflect https://gitlab.com/gitlab-org/gitlab/-/issues/334011
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/3wLvv6JyQvhy07Jxkvc630/Component-library?node-id=3050%3A0) `update-sidebar-component` branch
-
-### Screenshots
-
-Variants
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-Instances
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [x] **Maintainer**: Review and approve assignee’s changes.
-1. [x] **Maintainer**: Add the changes or additions to the target file. For
- example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [x] **Assignee**: Move your working file to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [-] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [-] **Assignee**: When applicable, [create an MR in this repository][new-gitlab-ui-mr] and apply the ""component-guideline"" template
- to create or update the component’s documentation page. If you do not have capacity, [create an issue in this repository using the ""Component documentation"" issue template][pajamas-component-documentation-template]. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: When applicable, [create an issue in GitLab UI using the ""Component"" issue template][gitlab-ui-component-template] to build or update the component code. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one.
-1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[pajamas-component-documentation-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-[new-gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new",2
-89563039,2021-06-30 19:40:55.756,Update component markdown template,"### Description
-
-Update the [example component documentation page template](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/pages/components/template.md) after https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2414 has been merged to reflect template updates.
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] Assign the correct component label to this issue.
-1. [x] Create an MR with the additions or updates needed.
-1. [-] When applicable, [create a new Pajamas issue using the ""Figma update"" issue template][pajamas-figma-update-template] to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [-] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a new GitLab UI issue using the ""Component""][gitlab-ui-component-template] issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [x] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/contribute/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",1
-89489145,2021-06-29 15:26:55.709,Add bot warning for workflow label and weight,"## Purpose
-
-In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/850 the UX Foundations team is working on adding workflow labels and weights to each issue. When a new issue is created there's no way for the author to know that a workflow label and weight should be added.
-
-The proposal is to have a bot notify the author to add the workflow label or weight, or to automatically add a label.
-
----
-
-Message:
-
-```
-Hi @[AUTHOR],
-
-Please add a [workflow label](https://about.gitlab.com/handbook/product-development-flow/) and [weight](https://about.gitlab.com/handbook/engineering/ux/ux-designer/#ux-weight-definitions) to your issue. This helps to categorize and locate issues in the future.
-
-Thanks for your help! :heart:
-
----
-
-You are welcome to help [improve this comment](LINK).
-```",2
-89486695,2021-06-29 14:47:29.804,Evaluate VPAT against GitLab v14.0,"## Purpose
-
-In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2434 we're updating the VPAT version to note that no material changes happened between 13.5 (date of current report) and 14.0. [More context](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1031)
-
-This effort evaluates 14.0 against the current VPAT report, makes any updates, and updates the version and report date in the VPAT.",2
-89416050,2021-06-28 14:55:53.428,Pajamas competitor analysis,"This issue is to discuss the possibility for doing competitor analysis for Pajamas. I think it will be valuable to do a lightweight version of the UX competitor analysis to gain insight into how we can continue to improve Pajamas, by taking a look at some other design systems.
-
-I think we have the opportunity to do something from scratch, I have heard from multiple designers that the current competitor analysis in UX is too in depth, perhaps we look at developing our own from scratch that's much simpler.
-
-- [ ] Determine whether doing a competitor analysis is useful
- - [ ] Determine how a formal competitor analysis will be structured",1
-88894335,2021-06-17 16:53:34.548,Where should research insights live that impacts Pajamas?,"## Purpose
-
-In a recent 1:1 I brought up the idea of using the wiki feature in the Pajamas project to house research insights and more conversational reasoning behind decisions that impact components. From each component page we could link to the relevant section of the wiki.
-
-This brought up the need to address a few questions at a higher level before solutioning:
-
-- Where should research live and how should it be incorporated into Pajamas (if at all)?
-- Is there still an insights repo that could be linked to?
-
-Currently, in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2414 as part of the component page template update a new ""Reference"" section is being added with the intent to add links and commentary.
-
-The component page documentation should be direct, and we don't want to add to the overhead by having research links throughout that might be private or change. So where could we have a SSoT and how should we reference it?",1
-88587817,2021-06-11 16:13:24.805,Tree > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the tree component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587816,2021-06-11 16:13:24.359,Tooltip > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the tooltip component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587815,2021-06-11 16:13:24.058,Token > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the token component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587814,2021-06-11 16:13:23.841,Toggle > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the toggle component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587813,2021-06-11 16:13:23.597,Toast > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the toast component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587811,2021-06-11 16:13:22.914,Tabs > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the tabs component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587809,2021-06-11 16:13:21.965,Table > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the table component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587808,2021-06-11 16:13:21.753,Spinner > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the spinner component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587807,2021-06-11 16:13:21.385,Sorting > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the sorting component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587806,2021-06-11 16:13:21.189,Socks > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the socks component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587805,2021-06-11 16:13:20.977,Skeleton loader > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the skeleton loader component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587804,2021-06-11 16:13:20.775,Segmented control > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the segmented control component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587803,2021-06-11 16:13:20.495,Search > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the search component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-88587802,2021-06-11 16:13:20.292,Radio button > Update docs to utilize new template,"## Background
-
-As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages.
-
-## Resources
-
-See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure.
-
-## Proposal
-
-Update the radio button component usage tab to be in alignment with the changes.
-
-This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1
-127230475,2023-04-26 19:42:12.971,UI kit > Clarify heading breakpoints,"## Description
-
-The breakpoint prefixes for heading styles can be perceived as available size options to be chosen from based on preference rather than sizes that need to be applied at a breakpoint.
-
-## Solution
-
-Make the size more verbose and clear by adding ""breakpoint"" and clarifying the range.
-
-[ View in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/HHCrSCelPUHKKK0d1QViMT/%F0%9F%93%99-Component-library?t=tGJp4jMMw0kkjMQM-11)
-
-**Example**:
-
-| **Before** | **After** |
-| ------ | ------ |
-| `UI/h1/sm` | `UI/h1/≤md breakpoint` |
-| `UI/h1/xl` | `UI/h1/≥xl breakpoint` |
-|  |  |
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [-] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360038512093) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [-] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [-] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [-] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [-] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [-] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [-] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [x] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [-] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [-] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [-] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [-] Make sure all layers are correctly named and organized.
-1. [-] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [-] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Consider adding a new version to the file's [version history](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history) to indicate the state prior to merging the changes. The name of the version and description of the changes are saved in the file history and provide a meaningful reference point.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-1. [x] If the file's version history isn't clear, [name the latest version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Name_an_existing_version) and update the details so it's clear what change had been made.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=manage-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-126941915,2023-04-19 20:09:02.337,Labels and linking,"## Purpose
-
->>In this context, the text “Code owners” isn't explicit that it navigates to the code owners file, because it's also used as a label for the list of code owners of the current file.
->
-> @pedroms I think this is a great point and something we should evaluate — should a label be allowed to link? And how does visual label relate to `label` (which wouldn't necessarily make sense in this context)? At the moment this text only visually appears as a label, and nothing about it, other than the preceding ':' indicates as much, which is why I'm inclined to proceed.
-
-Per the discussion in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/117251#note_1353052885, this issue is to discuss the following:
-
-- Should text that _appears_ as a label (although isn't actually a `label`) be allowed to link?
- - If yes, what link variant is most appropriate?
-
-For example, the ""Code owners"" text in the following screenshot.
-
-
-
-## Next steps
-
-- Document a decision in Pajamas.",1
-126288606,2023-04-05 14:22:54.150,Figma > Dropdown - decrease min-width,"## Description
-
-Decrease the min-width of the dropdown by 8px (16rem → 15.5rem) so that it fits within the new sidebar navigation.
-
-This would have minimal, if any, impact on existing instances and may even slightly improve some where all option text is short.
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-
-- [x] Update component and instances in Figma
-- [x] Create an issue to update in GitLab UI
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/n1QvO2JdlHIUUJUGsalyr0/%F0%9F%93%99-Component-library?t=EdntYrUvmvg1Uk3C-11)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [-] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360038512093) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [-] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [-] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [-] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [-] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [x] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [-] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [-] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Consider adding a new version to the file's [version history](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history) to indicate the state prior to merging the changes. The name of the version and description of the changes are saved in the file history and provide a meaningful reference point.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-1. [x] If the file's version history isn't clear, [name the latest version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Name_an_existing_version) and update the details so it's clear what change had been made.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=manage-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",2
-126156810,2023-04-03 09:25:19.835,Design tokens > Create page,"Create a placeholder page in Pajamas to point people towards when design tokens come up in conversation.
-
-This also provides a space for MRs to add a lightweight definition and document where we are starting and why.",1
-126018906,2023-03-30 21:43:35.918,Add new design-focused section to Pajamas,"## Purpose
-
-Create a new section in the Pajamas website to house DesignOps content and make the UI kit documentation more visible and structured.
-
-### Proposed structure
-
----
-
-**DesignOps**
-
-- Component lifecycle
-- Pajamas UI Kit
- - _Sections from the current md file…_
- - Release notes
-
----
-
-The content in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md to this section to break it out into sub pages, make it available in Pajamas search, and have better formatting for visuals.",2
-124789766,2023-03-06 11:31:28.589,Link > Finalise design specs,"Issue to track efforts to finalise the design specs for links
-
-# Proposed link styles
-
-The following documents the intention, rather than the prescription for the actual CSS to be used.
-
-Class names placeholder to make it easier to read.
-
-There are certainly better ways to achieve the same thing.
-
-[Play with the styles in context in this codepen](https://codepen.io/danmh/pen/rNZGKbm).
-
-```scss
-
-// Inline links assumed the default
-
-a {
- color: $blue-700;
- text-decoration: underline;
- text-decoration-color: rgba($blue-700, .72); // allows underline tone to match background
- text-underline-offset: 2px; // we should make this a relative value,
- // as it breaks when the browser font size is changed
- transition: background-color 100ms linear, color 100ms linear,
- border 100ms linear, text-decoration-color 100ms linear;
- // builds on existing link transition styles, adds text-decoration-color
-
- &:hover {
- color: $blue-800;
- text-decoration: underline !important; // allows other link types to have underline on hover
- // even if they have text-decoration: none for the rest state
- text-decoration-color: currentColor;
- }
-
- &:focus-visible {
- color: $blue-800;
- text-decoration: underline !important;
- text-decoration-color: currentColor;
- outline: 2px solid #428fdc; // existing focus styles
- outline-offset: 2px; // existing focus styles
- }
-
- &:active {
- color: $blue-900;
- text-decoration: underline;
- text-decoration-color: currentColor;
- transition: none; // makes the click or press feel snappy
- }
-}
-
-a.ui-link {
- text-decoration: none; // no underline in rest state
-}
-
-a.meta-link {
- text-decoration: none;
-
- &.meta-link-dark {
- color: $grey-900;
- &:hover {color: $grey-950;}
- &:active {color: $black;}
- }
-
- &.meta-link-subdued {
- color: $grey-700;
- &:hover {color: $grey-800;}
- &:active {color: $grey-900;}
- }
-}
-
-a.mention {
- padding: 0 2px; // these are no change from existing styles
- background-color: $blue-100;
- border-radius: 4px;
- text-decoration: none;
-
- &.mention-current {
- background-color: $orange-100;
- }
-}
-```
-
-## Rational
-
-Why blue-700
-Why opacity
-Why underline at all
-etc
-etc
-
-### Next
-
-- [ ] https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1551+
-
-### Unblocks
-
-- [ ] https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/880+
-- [ ] https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1217+
-- [ ] https://gitlab.com/gitlab-org/gitlab-ui/-/issues/1084+
-- [ ] https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1536+
-- [ ] https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1554+
-
-
-### Related to
-
-- https://gitlab.com/gitlab-org/gitlab/-/issues/336819+",2
-124619714,2023-03-02 12:03:45.318,Add structure visual and list. for link,"### Description
-
-
-
-Add link structure diagram
-
-Related to: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1444+
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] Assign the correct component label to this issue.
-1. [x] Create an MR with the additions or updates needed.
-1. [~] When applicable, [create an issue using the `Figma update` issue template][pajamas-figma-update-template] to update the component in Figma, and mark it as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [~] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template]. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [~] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",1
-124074239,2023-02-21 18:18:30.834,Breadcrumb component updates,"# Breadcrumb
-
-The breadcrumb is a component that is less isolated than other components because it’s navigation based on the page it’s within, and is bound by the layout and behavior constructs of that page along with other content and functionality.
-
-Updates to the breadcrumb can’t happen without considering the impact to its own UX, and to the UX of the page in which it’s placed. For that reason, there are two parallel categories of considerations that have to be addressed: component-specific, and the relationship with other elements.
-
-## Component-specific
-
-View details
-
-- Responsive - Wrapping and truncation
- - Truncation based on width or character count? Both?
- - Where truncation occurs in the string?
- - At wider views, should we allow larger strings to be expanded, potentially creating an unwieldy string in primary real estate?
-- States
- - Interactive states, such as hover and focus
- - Current page state
-- Design spec updates (border, separator, states, etc.)
-- Semantics and [accessibility updates](https://gitlab.com/groups/gitlab-org/-/epics/6879) for current implementation
-- Migration
-
-**Deliverables:**
-
-- [Updated design specs](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1533)
-- Updated Pajamas documentation
-- Component updates in GitLab UI
-- Component migration
-
-
-
-## Relationship with other elements
-
-View details
-
-- **[Navigation](https://gitlab.com/gitlab-org/gitlab-ui/-/issues/2141) — specifically the sidebar show/hide icon placement and behavior (priority)**
-- DOM order with other elements, like alerts, banners, and broadcast messages
-- Within [headers](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/3263)
- - Sticky behavior
- - Page actions
-- Fluid and fixed width layout settings
-
-**Deliverables:**
-
-- **Navigation + breadcrumb requirements and specs (priority)**
-- Identify and document potential patterns that use a breadcrumb
-- Updated Pajamas documentation
-
-
-
-## Resources
-
-- [A collection of 40+ breadcrumb components from various design systems](https://arc.net/e/F3F0AA49-51B1-4254-BD21-A450640C83E1)
-- [Pajamas > Breadcrumb](https://design.gitlab.com/components/breadcrumb)
-- [GitLab UI > Breadcrumb](https://gitlab-org.gitlab.io/gitlab-ui/?path=/story/base-breadcrumb--default)",5
-123176841,2023-02-07 07:51:38.155,Dropdown > Document height options,"### Description
-
-Document height options (fit contents height vs. fixed height). There are use cases where we want the dropdown to shrink to it's content (fit contents) and others where we want to keep its initial height (fixed height).
-
-| Contents size | Keep initial height |
-| ------ | ------ |
-|  |  |
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [X] Assign the correct component label to this issue.
-1. [ ] Create an MR with the additions or updates needed.
-1. [ ] When applicable, [create an issue using the `Figma update` issue template][pajamas-figma-update-template] to update the component in Figma, and mark it as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template]. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",1
-122956530,2023-02-02 17:03:00.874,"fix: Add missing ""Contribute"" tabs","## Purpose
-
-Some component pages are missing the ""Contribute"" tab.",2
-122852029,2023-02-01 15:14:25.849,Figma > Button - Add states,"## Description
-
-This MR adds missing states to the main components (hover, focus, active).
-
-### Figma file
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/4VRjxqlOB94BomdQfBNioe/%F0%9F%93%99-Component-library?node-id=425%3A7&t=XFUiIlIv43Z2bxqU-11)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [X] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [X] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [X] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [X] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360038512093) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [x] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [x] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [ ] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [ ] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [ ] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Consider adding a new version to the file's [version history](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history) to indicate the state prior to merging the changes. The name of the version and description of the changes are saved in the file history and provide a meaningful reference point.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-1. [x] If the file's version history isn't clear, [name the latest version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Name_an_existing_version) and update the details so it's clear what change had been made.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=manage-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-122830518,2023-02-01 10:46:33.881,Figma > Toggle - Add states,"## Description
-
-This MR adds the missing states to the badge component.
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-### Figma file
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/QXWDiFqaiOZVtKXdheEc49/%F0%9F%93%99-Component-library?node-id=425%3A140&t=WDnJTGhTFcT4t2TZ-11)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [X] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [X] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360038512093) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [-] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [-] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [-] Consider adding a new version to the file's [version history](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history) to indicate the state prior to merging the changes. The name of the version and description of the changes are saved in the file history and provide a meaningful reference point.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-1. [x] If the file's version history isn't clear, [name the latest version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Name_an_existing_version) and update the details so it's clear what change had been made.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=manage-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-122729768,2023-01-31 05:05:26.187,Update inline text link hover/focus style to align with docs,From !3205 We currently don't change the color for inline text links on design.gitlab.com so this might be something we should update to align with guidance here in later iterations.,1
-122515620,2023-01-26 21:30:20.938,Figma > Tertiary button multiply,"## Description
-
-The tertiary buttons use `mix-blend-mode: multiply` ([source](https://gitlab.com/gitlab-org/gitlab-ui/-/blob/main/src/components/base/button/button.scss#L326)) to keep contrast consistent when on different background colors. This updates them in the UI kit to match.
-
-
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/TT1EM05P5ALuyJv017MFXf/%F0%9F%93%99-Component-library?node-id=425%3A7&t=qOSChFXfSNeeKAdK-11)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [-] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [-] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [-] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [-] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [ ] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [-] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [-] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [-] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [-] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Consider adding a new version to the file's [version history](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history) to indicate the state prior to merging the changes. The name of the version and description of the changes are saved in the file history and provide a meaningful reference point.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-1. [ ] If the file's version history isn't clear, [name the latest version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Name_an_existing_version) and update the details so it's clear what change had been made.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-122318319,2023-01-23 17:42:41.455,Dropdown > Update design spec to include min/max width,"## Purpose
-
-Based on the implementation plan in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1507#implementation-plan, the **dropdown** design specs should be updated to include the recommended minimum and maximum widths.
-
-This doesn't have to be a component setting, but that is an option if the configuration is easy enough to implement and the design experience isn't impacted.
-
-## Specs
-
-Make dropdown's width more flexible:
-
-* [x] min-width: 16rem (256px)
-* [x] max-width: 28.5rem (456px)
-* [x] max-height: 19.5rem (312px)",2
-121186565,2023-01-03 19:31:36.320,Broadcast message > Update variants and instances,"## Description
-
-Updating the broadcast message component in Figma to:
-
-- Better account for fixed vs. fluid layout behavior.
- - Max-width (954px) is calculated based on the [990px fixed width](https://design.gitlab.com/product-foundations/layout#fixed-layout) minus 16px margin on each side.
-- Add description for each variants. Description is visible in the properties panel when an instance is selected.
-- Add ability to toggle × close icon.
-- Add instances for different states and [example] themes.
-- Remove unnecessary todo and note.
-
-The changes are modeled after what's currently in place for the [alert component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/%F0%9F%93%99-Component-library?node-id=425%3A1&t=zd18xI1uNlssCjAi-11).
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/J0xjeC3YBsx0AeJJx3cGf7/%F0%9F%93%99-Component-library?t=mg4lYg8ii8OcZgwZ-11)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [-] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Consider adding a new version to the file's [version history](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history) to indicate the state prior to merging the changes. The name of the version and description of the changes are saved in the file history and provide a meaningful reference point.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-1. [ ] If the file's version history isn't clear, [name the latest version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Name_an_existing_version) and update the details so it's clear what change had been made.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-121174687,2023-01-03 16:25:24.204,"Dropdown > Direction for rendering overflowing, non-wrapping text within items","In some cases, we might need to display long non-wrapping texts within a dropdown's items. For example, the notification settings display the user's emails, which might overflow the dropdown menu:
-
-
-
-## Implementation plan
-
-- [ ] `GlTruncate`: ensure the rendered element has an accessible `aria-label` attribute.
-- [ ] `GlCollapsibleListbox`
- - [ ] Make dropdown's width more flexible:
- - [ ] `min-width: 15rem`
- - [ ] `max-width: 28.5rem`
- - [ ] Leverage `GlTruncate` to truncate long items' names. This should be probably be the consumer's responsibility, so this can be a recommendation in the docs.
-- [ ] Ensure the notifications settings render properly as per https://gitlab.com/gitlab-org/gitlab/-/issues/373843#note_1227467886.",2
-120713314,2022-12-20 20:03:20.601,Figma > File uploader enhancements,"## Description
-
-Address the following items from https://gitlab.com/gitlab-org/gitlab-ui/-/issues/297:
-
-Component overrides
-
-### Component property user experience
-
-#### Conditional properties
-
-Changing some of the component properties can override previously selected options.
-
-
-
-There is opportunity to improve the user experience here by only showing properties relevant to the selected variation.
-
-#### Retaining overrides
-
-Some overrides are not retained when switching versions
-
-
-
-
-
-Recreating the current UI
-
-### Recreating the current UI
-
-Using this component it is not possible to recreate the current UI.
-
-
-
-
-
-Slider considerations
-
-Moved to it's own issue -> https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1511+
-
-
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/ccOwOGUNWttGmmMalGjzMQ/%F0%9F%93%99-Component-library?node-id=8000%3A0&t=OsyuPWkvpYs3s9jK-11)
-
-
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [ ] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [ ] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [ ] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Consider adding a new version to the file's [version history](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history) to indicate the state prior to merging the changes. The name of the version and description of the changes are saved in the file history and provide a meaningful reference point.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-1. [x] If the file's version history isn't clear, [name the latest version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Name_an_existing_version) and update the details so it's clear what change had been made.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",2
-120437029,2022-12-14 21:43:28.735,Figma > Form elements remove warning state,"## Description
-
-The warning (orange) state for form elements isn't present in GitLab UI, and it was determined that there isn't a need for it via https://gitlab.com/gitlab-org/gitlab-ui/-/issues/1809.
-
-This issue is to remove the warning state from the form elements in Figma, and to remove any mention of it Pajamas.
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/qnl2lq49gLpti4TFUCNlhm/%F0%9F%93%99-Component-library?node-id=49840%3A75722&t=0qOhvYOSwOznoAf7-11)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [-] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [-] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [-] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [-] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [-] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [-] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [-] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [ ] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Consider adding a new version to the file's [version history](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history) to indicate the state prior to merging the changes. The name of the version and description of the changes are saved in the file history and provide a meaningful reference point.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-1. [x] If the file's version history isn't clear, [name the latest version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Name_an_existing_version) and update the details so it's clear what change had been made.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",2
-120174557,2022-12-09 19:05:39.341,Figma > Tooltip – Update tooltip component to resize based on content,"## Description
-
-The tooltip component currently doesn't resize based on content. Additionally, if you change the tip position, the content isn’t persisted. See [discussion in Slack](https://gitlab.slack.com/archives/CNDGX396C/p1670605977187449) and example:
-
-
-
-We should update the component to fix these issues.
-
-
-
-
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/UXgoH1IanB4jxRctxXEt50/%231469-tooltip-resize-danmh?node-id=425-142)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [~] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [x] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Consider adding a new version to the file's [version history](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history) to indicate the state prior to merging the changes. The name of the version and description of the changes are saved in the file history and provide a meaningful reference point.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-1. [x] If the file's version history isn't clear, [name the latest version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Name_an_existing_version) and update the details so it's clear what change had been made.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",2
-119333804,2022-11-24 14:14:01.574,Figma > Pagination - Refactor component,"## Description
-
-Refactored the Pagination component to use Variants for the pagination items. Also updated the focus style of the component.
-
-### Figma file
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/LbJ6WDv08Iznll87TfoOin/%F0%9F%93%99-Component-library?node-id=425%3A130&t=4ijE7d28kTS0Ys92-0)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [x] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",2
-119246695,2022-11-23 10:16:26.707,Figma > Dropbutton - Friendly text first,"## Description
-
-This is a follow-up to https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1465+ and updates the Dropbutton component to use the friendly text first for filters.
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/NJNiIFOFovDtXJWmMHQY16/%F0%9F%93%99-Component-library?node-id=65182%3A99209&t=Pj6CvbqbaGv71jCQ-1)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [x] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-119246302,2022-11-23 10:10:08.478,Figma > Token - Update Focus,"## Description
-
-Updates the focus to make use of the focus helper component.
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/v4EklPE0xEbS54bngpqjgx/%F0%9F%93%99-Component-library?node-id=425%3A141&t=1OP5Fz5ygJ9NcnCr-0)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [x] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [x] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-118936476,2022-11-17 19:57:44.973,Button > Add note about icon indicating action,"## Purpose
-
-Icon only buttons shouldn't act as a toggle where the icon might change depending on state. For example,  changing to  on click because the state can be confusing. Does it mean that the current state is A and clicking goes to B, or the opposite?
-
-This issue is to initiate documenting the recommendation.",1
-118776570,2022-11-15 22:42:35.204,Update severity guides for errors,"## Purpose
-
-In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/contents/usability/error-prevention.md?plain=1#L13 there's reference to old button content that can be updated. Along with the the entire section will reviewed to make sure it's accurate.
-
->The destructive action can easily be undone and no actual data was lost. Consider adding no friction at all in order to streamline the interface, especially in places where the action needs to be performed in bulk. These kinds of destructive actions can be exempt of being **[elementary](/components/button/#elementary) styled and can instead be [neutral](/components/button/#neutral) styled buttons.** (Emphasis added)",1
-118773554,2022-11-15 21:26:13.349,Pajamas navigation refinements,"## Purpose
-
-A followup from #1443 to further refine the navigation with the following:
-
-- Update the Pajamas lockup and ensure a common left edge (alignment) for all elements.
-- Ability to expand multiple sections at once. This is a common accordion-like pattern that would allow a user to compare the options in different sections. While this UX might not be ideal for some sites, it can be a benefit for a user of Pajamas to get a better understanding why there are **Form elements** in one section, and **Forms** in another.
-- Sticky expanded sections. Since some sections (like **Components**) are quite long, having the parent category item sticky when expanded can help a user maintain context for the current section they're navigating.
-- Update design of search to be more integrated into the sidebar (inspired by the recent update to the dropdown design).
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-
-[ View the working file in Figma →](https://www.figma.com/file/qYQOk3DhrswWIsRnoUTJ6J/%231378-Pajamas-IA-JE?node-id=708%3A4482&t=TDoghMezobgvIbnA-11)
-
-**Note:** The _before_ screenshot is from !3115's review app.",3
-118771757,2022-11-15 20:29:49.833,Figma > Update button size and position in dropdowns,"## Description
-
-- Buttons in a dropdown ([disclosure](https://design.gitlab.com/components/dropdown-disclosure) only) could use the sm size since they're already in a smaller container and supporting a larger context.
-- Buttons in a dropdown ([disclosure](https://design.gitlab.com/components/dropdown-disclosure) only) should be right positioned to follow [alignment](https://4456656-review-1443-updat-77up3w.design-staging.gitlab.com/) guidelines since they are in a constrained container.
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-|  |  |
-
-[ View working branch in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/Ec1j6iY0dkjujPqhR8mxMw/%F0%9F%93%99-Component-library?node-id=65182%3A99209&viewport=-2770%2C229%2C1&t=KsEY2muucemu16ht-11)
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/Ec1j6iY0dkjujPqhR8mxMw/%F0%9F%93%99-Component-library)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [ ] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [ ] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [ ] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [ ] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [ ] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [ ] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [ ] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [ ] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-118758205,2022-11-15 16:03:32.458,Pajamas site mobile nav,"## Purpose
-
-As a followup to !3115 there are some additional improvements needed for the mobile navigation of the Pajamas website.
-
-From https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/3115#note_1171724042:
-
-> …move from a partial cover to a full-width/overlay menu to:
->
-> 1. Add a close button in correct focus order, potentially using a × icon
-> 1. Remove overflow scroll of page content while menu is open (swipe moves content body not menu items)
-> 1. Allow increase in touch targets in menu for mobile
-> 1. Rethink ≡ overlapping page content on scroll",3
-118643439,2022-11-14 04:49:31.441,Homepage images sizing on small screens,Update homepage styles so that images load correctly on mobile. Fix layout to avoid x-axis overflow on smaller screens e.g. `320px`.,1
-118458939,2022-11-10 00:20:20.315,Update documentation heading border styles,"Update heading `border-bottom` styles to be consistent with tab border color.
-
-Tighten `padding-bottom` to improve vertical rhythm between headings and related content.",1
-118368014,2022-11-08 16:38:04.314,Figma > Remove alert in modal example,"## Description
-
-Per [Pajamas](https://design.gitlab.com/usability/error-prevention#severity-guidelines):
-
->Avoid using alerts to emphasize the content inside a modal.
-
-and…
-
->Any final confirmation that is destructive must use the danger variant (unless a browser dialog is used).
-
-This removes the alert from the modal example content and reformats the text.
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/WaECLxx4sHP5BfyWgIXYmp/%F0%9F%93%99-Component-library?node-id=425%3A129&viewport=-90%2C25%2C0.93)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [ ] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [ ] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [ ] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [ ] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [ ] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-118308894,2022-11-07 20:54:31.002,Figma > Broadcast message use paragraph style,"## Description
-
-Use paragraph style instead of label and address any layout regressions (will match GitLab UI).
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/7pJYvD1VtVfHDvWW7zWump/%F0%9F%93%99-Component-library?node-id=425%3A6&viewport=835%2C400%2C0.8)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [ ] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [ ] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [ ] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [ ] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-118308781,2022-11-07 20:51:23.656,Figma > Accordion use paragraph instead of labels style,"Update text styles and address any layout regressions (will match GitLab UI).
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-
-[View working branch in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/4ytND6X78TA9d8IPJGpYJv/%F0%9F%93%99-Component-library?node-id=425%3A0)",1
-118136795,2022-11-04 10:34:40.096,Figma > Merge request reports - update non-ui kit components,"## Description
-
-
-
-
-
-Merge request reports page uses non-ui kit components.
-
-Issue to switch them to use UI Kit versions.
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-Also added the full stop :smile:
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/fAr4qmF4D71mTFF7s8Bn6D/%F0%9F%93%99-Component-library)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [ ] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [ ] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-118079628,2022-11-03 12:47:46.558,Figma > File uploader - Fix instances to use linked components,"## Description
-
-
-
-
-
-There are detached instances in the file uploaded examples.
-
-Issue to reattach those that can be and ensure correct styles and components are used.
-
-https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/%F0%9F%93%99-Component-library?node-id=8000%3A1
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](ADD LINK TO FIGMA FILE/FRAME)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [ ] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [ ] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [ ] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [ ] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [ ] Update the link to the working file under the **Figma link** section below.
-1. [ ] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [ ] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [ ] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [ ] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [ ] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [ ] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [ ] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [ ] From the dropdown to the right of the file name, select ""Request review"".
-1. [ ] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [ ] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [ ] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [ ] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",2
-118001916,2022-11-02 11:44:44.689,Move gl- utils to GitLab UI,"In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/3113, we have added a few `gl-` CSS utils to support a cleanup initiative. We should eventually move those and any additional utils to GitLab UI.",1
-117950973,2022-11-01 15:36:42.132,Cleanup error page layout,"The following discussions from !3050 should be addressed:
-
-- [x] @pgascouvaillancourt started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/3050#note_1136458211):
-
- > **nitpick(non-blocking):** We are repeating the `typography gl--flex-center gl-flex-direction-column gl-h-100vh` wrapper both here and in the `page-not-found` component. Perhaps we could de-duplicate this.
-
-- [x] @pgascouvaillancourt started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/3050#note_1136458215):
-
- > **thought(non-blocking):** We seem to be repeating a lot of code from the default layout here. I wonder if we could conditionally render the footer instead of creating a new layout, it would make things a bit easier to maintain.
-
-- [x] @pgascouvaillancourt started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/3050#note_1136458218):
-
- > **nitpick(non-blocking):** This might not be relevant in this layout since the homepage uses the default layout anyways.",2
-117759458,2022-10-28 14:26:52.192,Tint neutral palette based on brand,"## Purpose
-
-In the latest brand updates the brand palette includes neutrals that are slightly more cool (blue) in tone. The current Pajamas neutral palette is completely desaturated and feels more generic than it could. There have been previous efforts to explore introducing both a cool and warm set of neutrals to compliment the current ones, however it became clear that this would be to try and account for the current theme approach (warm neutrals with red theme for example), and add unnecessary complexity to an already minimally used feature.
-
-Having a neutral palette that skews more towards the temperature of the brand palette will provide more continuity between digital properties and subtly allow us to infuse more of the brand into Pajamas and the product. Given our use of blue for primary actions and links, a more cool palette also helps elements to feel more harmonious.
-
-## Proposal
-
-Update the neutral palette to align with the grays in the brand palette.
-
-| | **Palette** |
-| ------ | ------ |
-| Brand |  |
-| Current neutral |  |
-| Proposed neutral |  |
-
-**[ View working file in Figma →](https://www.figma.com/file/tjSjgnxomkqPg8BEhPdNFJ/%231452-tine-neutral-palette-%40jeldergl?node-id=0%3A1)**
-
-**[ View UI kit branch in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/XRCIH8ZdaAbyBpkJzgxdKG/%F0%9F%93%99-Component-library)**
-
-**[🎨 View palette in Huetone→](https://huetone.ardov.me/?palette=N4IgdghgtgpiBcIDiAZABAORgVwC4CcIAbAZxABoQALbGM%2BAbVElgRCz0KIpAGMB7Iv3z0GIAMQAzAKwyZPKQAZJyxQoAmAIy1aFmyfv0KAnKbMKAHADZr1hVYeOF0mC5fOATNK8eFAFkUAgIUAZkUwsIUARkkYmJAAXQBfcmZoOEQOAmI0AUEeASERBDEpfQhJdQUYXhqYSQ1edSa4SnFDSV4QhQg-CBCIC0tjC1GqtoB2EImPCaG2qw8rKJtnEOko6XmJPxC-Dz9t8RCTjxCjuJgDxJS01kQAIUIwcb5BYVEJSW%2BfjSj1RTqbptdT-QHAiQQDwQKIQKw9aGw%2BGTPwTKITCAKCao9GYtp%2BaT7PyvcQEokkjyaDwWc4KSnU2ltdFREIeKI3BKUXD8MB0EogKJqSjSIUCxSijzinhhUUBUUi0VWKWUCbKkAWNXGTUim5AA)**
-
-**Other thoughts…**
-
-Yes, this is subjective and nuanced. When exploring navigation updates both in the product, and Pajamas, designers have noted that the current neutrals are just too flat. We have an opportunity to better align the recent brand work and the product, and this is a very subtle, but effective way to do so.
-
-A cool neutral palette could also benefit dark UI and ironically (ignoring the terms) prevent it from feeling too cold or bland. [From this article](https://compilezero.medium.com/dark-mode-ui-design-the-definitive-guide-part-1-color-53dcfaea5129):
-
-> …you could also use accented neutrals instead of a pure-grey palette, which I personally recommend using due to 2 main reasons,
->
-> _Pure greys are not found naturally, and so its a good option to have some tint on those neutrals to give it a more natural vibe._
->
-> _Tinted neutrals, could help give the UI an overall emphasized tone and emotion to look forward to._
-
-**Resources**
-
-- https://designerup.co/blog/practical-guide-to-perfect-ui-color-palettes/
-- https://compilezero.medium.com/dark-mode-ui-design-the-definitive-guide-part-1-color-53dcfaea5129
-- https://graphicdesign.stackexchange.com/questions/119887/dark-ui-design-why-tint-the-dark-gray-colors-with-a-different-primary-color
-- https://atmos.style/blog/lch-color-space
-- https://stripe.com/blog/accessible-color-systems",2
-117214787,2022-10-20 06:03:01.410,"Pajamas Migration Day: December 2, 2022","As part of our ongoing [component migration push](https://gitlab-org.gitlab.io/frontend/epic-burndown-charts/fy23-q1/), we are hosting another Pajamas Migration Day!
-
-- **When:** December 2, 2022
-- **Who:** Everyone! FE, BE, Designers, Product, etc. Everyone is encouraged to contribute.
-- **Where:** Your very own home or work space, but also join the `#pajamas_migration_day` slack channel to hang out and chat with fellow contributors!
-- **Why:** We want to encourage a day of migrating legacy components / css to use Pajamas!
-- **Bonus:** If you contribute three merge requests on Pajamas Migration Day, you can expense a meal for up to $25 USD! Please use the ~""Pajamas Migration Day"" and ~""FY23::Q4"" labels on your MRs to be eligible. In Expensify, use the `Meals Company Provided (Non-Client related)` category.
-
-**Need help?** Ping any member of the [Foundations team](https://about.gitlab.com/company/team/?department=manage-foundations-team) for support or help throughout the day. We are here to assist!
-
-## How to contribute
-
-**If you are working on building your coding skills, check out these issues:**
-
-- [HAML: Buttons](https://gitlab.com/groups/gitlab-org/-/issues/?sort=created_date&state=opened&label_name%5B%5D=Pajamas%20Migration%20Day&label_name%5B%5D=workflow%3A%3Aready%20for%20development&label_name%5B%5D=component%3Abutton&label_name%5B%5D=haml%20migration&first_page_size=20)
-- [HAML: Cards](https://gitlab.com/groups/gitlab-org/-/issues/?sort=created_date&state=opened&label_name%5B%5D=Pajamas%20Migration%20Day&label_name%5B%5D=workflow%3A%3Aready%20for%20development&label_name%5B%5D=component%3Acard&label_name%5B%5D=haml%20migration&first_page_size=20)
-
-**If you are confident in your coding skills, check out these issues:**
-
-- [Dropdown migrations](https://gitlab.com/groups/gitlab-org/-/issues/?sort=created_date&state=opened&label_name%5B%5D=OKR&label_name%5B%5D=component%3Adropdown&assignee_id=None&first_page_size=20)
-- [Remove select2 implementations](https://gitlab.com/groups/gitlab-org/-/epics/8738)
-- [Extract Page Specific CSS Files](https://gitlab.com/groups/gitlab-org/-/epics/3694)
-
-**Tip:** There does not need to be a specific issue open to contribute! Starting with MRs that migrate legacy code is a great way to contribute to the effort. If there are no issues to pick up, treat the day like a scavenger hunt!
-
-**Reminder:** Please add the ~""Pajamas Migration Day"" and ~""FY23::Q4"" labels to your MRs, as well as the specific component label that relates to your change (for example: ~""component:alert"")",0
-117042973,2022-10-17 15:01:53.774,Add Mermaid diagram capabilities,"In a recent Foundations Open Office Hours meeting we discussed the need to add decision trees, and part of the discussion was what format these should take: Figma embed, SVG, Mermaid, etc. Mermaid would be ideal to keep it in the source and manage changes.",3
-116787230,2022-10-12 23:05:06.327,Update Pajamas navigation as a result of #1378,"## Purpose
-
-Update the Pajamas navigation (and related pages) based on conclusions and direction from the results of #1378.
-
-## Scope
-
-- Update the navigation structure.
-- Update the navigation semantics to ensure accessibility.
-- Update navigation design.
-
-## Direction
-
-[📐 Prototype →](https://codepen.io/lostsatellites/full/rNvbrao)
-
-",3
-116774125,2022-10-12 18:24:03.009,Dropdown > Update docs to align with latest approach,"## Purpose
-
-As a next iteration we've discussed moving the listbox to a low-level component. What that means is that it isn't something to be used on it's own as an actual dropdown variant, but instead it's consumed by both the disclosure (optional) and combobox (required).
-
-Likewise, it's been determined that the menu variant isn't something we'll proceed with for now since the disclosure can fir the use cases we have today in the product.
-
-## Changes
-
-- Place necessary listbox content within the [combobox](https://design.gitlab.com/components/dropdown-combobox) page.
-- Deprecate the [listbox](https://design.gitlab.com/components/dropdown-listbox) page.
-- From the [disclosure](https://design.gitlab.com/components/dropdown-disclosure) page, link to the new listbox section under combobox as the SSoT.
-- Deprecate the [menu](https://design.gitlab.com/components/dropdown-menu) page.
-- Consider adding decision trees in the _when to use_ section(s) to help determine what to use.
-
-The above changes would leave us with only the disclosure and combobox dropdown variants. To avoid the use of a menu-like option, we could consider adding a line about what `role= menu` is and why we don't use it in both places.",1
-116569759,2022-10-10 10:17:17.158,Disable Google Analytics (and therefore remove Cookie Banner) for design.gitlab.com,"The cookie banner breaks stuff, see for example:
-
-- https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1436
-- https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/commit/15be27162585b06eb2d390cf0191890100a5622c
-
-If we do not ship Google Analytics, we need no Cookie Banner, because we are not using Cookies otherwise.
-
-Given that noone seems to have looked at Analytics in a while (at least when I asked), we should consider removing it and making our lives easier.",1
-116409347,2022-10-06 14:10:38.220,Figma > New Illustration for scheduled actions,"## Description
-There's no illustration available in the library for any scheduled activity in the platform. We use and old and very specific illustration for [scheduled pipelines](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/pipeline_schedules but there's a need for something more generic that can be re-used in other contexts as well.
-
-There's a need to add an empty state to the `Scheduled pipeline` page for which this illustration will come in handy.
-
-| Current empty state for pipeline schedule page |
-|-------|
-|  |
-
-
-
-
-
-### Concept
-
-A simple illustration using the latest [illustration guides](https://design.gitlab.com/product-foundations/illustration/) that can universal represent the concept of ""schedules,"" ""scheduling,"" ""scheduled,"" and similar forms.
-
-### Figma file
-TBD
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/1ui9w228X0S5WxaD0SRdIA/branch/k2RyJnTszVzFWLKr9UsvZO/Illustration-library?node-id=441%3A2008)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [-] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [-] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [ ] Update the link to the working file under the **Figma link** section below.
-1. [ ] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [ ] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [ ] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [ ] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [ ] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [ ] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [ ] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [ ] From the dropdown to the right of the file name, select ""Request review"".
-1. [ ] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [ ] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [ ] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [ ] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-
-
-/labels ~Figma ~""Pajamas UI Kit"" ~""pajamas::design""",2
-116091745,2022-09-30 18:49:41.164,Discovery > Look into possibilities of displaying ViewComponents in Pajamas,"Now that we have [ViewComponents](https://gitlab.com/groups/gitlab-org/-/epics/8113), it would be great to get those displayed in Pajamas alongside the Vue components.
-
-As a first iteration, the `Implementation` tab could change to `Vue` and we could introduce a new tab per component called `View`.
-
-One potential hurdle is that it needs to properly deployed to a Rails application, so we need to determine if this is possible or what options we have.
-
----
-
-@thutterer
-
-> Prototype at https://gitlab.com/gitlab-org/frontend/playground/lookbook-app",3
-116025904,2022-09-29 16:29:00.603,Typography: Update Figma to use new default fonts,"## Description
-
-Update all Pajamas UI Kit assets in Figma to use the shipped version of Inter, which includes variable features.
-
-## Scope
-
-All [Pajamas UI Kit](https://www.figma.com/files/project/3802635) files:
-
-- Component library
-- Product icons (labels only)
-- Product pages
-- Data visualization
-- Type scale - Documentation markdown
-- Type scale - Compact markdown
-
-Other:
-
-- Templates
-- Cover slide
-
-### Out of scope
-
-- Updating existing design files
-
-## Related
-
-The [Type Fundamentals](https://design.gitlab.com/product-foundations/type-fundamentals) page in Pajamas would eventually need to be updated with the latest font stack info.
-
-### Figma test
-
-- [Component library →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/HIA8tpxKnRBR7bFP901AsS/%F0%9F%93%99-Component-library?node-id=440%3A0)
-
-### Figma branches
-
-- [Component library →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/WM9pPOVoiGnI17U0PSD2os/%F0%9F%93%99-Component-library?node-id=3050%3A0)
-- Product icons (labels only)
-- Product pages
-- Data visualization
-- [Type scale - Documentation markdown →](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/branch/nTHaYuIrt7fMmSBrowA9uz/Type-scale---Documentation-Markdown?node-id=3%3A54)
-- [Type scale - Compact markdown →](https://www.figma.com/file/mjAZxHkK95TlQ6L14aNp2M/branch/9LMZJBsTtQqMGPbrH8Q07Q/Type-scale---Compact-Markdown?node-id=3%3A54)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [ ] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [ ] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [ ] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [ ] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [ ] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [ ] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [ ] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [x] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",3
-113900144,2022-08-26 07:30:21.301,Add structure image for filter,[View working file in Figma (branch) →](https://www.figma.com/file/2XRq1MnIG69iti76Mh9HpJ/branch/X3R2AZyGx5IEAd2IqrMdTj/Pajamas-visual-examples?node-id=9981%3A21053),1
-113719597,2022-08-23 18:36:18.708,Introduce option to put selected items at top of dropdown,"## Problem to solve
-
-Without a dropdown pattern that shows the selected items at the top, I can't see what those selections are without a lot of scrolling in the dropdown. The truncation in the button suggests that there are more items, but how do I know what these are? Example from https://gitlab.com/gitlab-org/gitlab/-/issues/345430/designs/Runner_tag_field_states.png#note_1074738137:
-
-![]()
-
-I'd have to scroll down through potentially hundreds of items to see what the `+2 more` refers to (and/or to unselect them). Sometimes the dropdown doesn't even show the complete list, which makes it impossible to find it unless I know what I'm looking for and can use the search to find it (and unselect it, for example).
-
-## Proposal
-
-| 5 items | 6+ items creates a scrollable area |
-| ------ | ------ |
-|  |  |
-
-In order to prevent the selection from moving around within the input, which could be a frustrating and disorienting experience, the selection should move _after_ the dropdown is closed so it's shown when it's re-opened. This is different than how it currently works in the Assignees dropdown.
-
-Example:
-
-
-
-As far as I can tell, this type of dropdown isn't available in [Pajamas](https://design.gitlab.com/components/dropdown-listbox), [gitlab-ui](https://gitlab-org.gitlab.io/gitlab-ui/?path=/story/base-dropdown--default), or the Figma library as a variant (only as an [instance](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/%F0%9F%93%99-Component-library?node-id=12053%3A6)).",5
-113627776,2022-08-22 12:25:32.913,Typography scale(s) exploration,"Update typography scale(s) and make use of them in GitLab UI & the product.
-
-- Can we unify some of the scales?
-- Build a new scale with variables so it can be optimised to different usecases
-- Presenting type scales in GitLab UI and Pajamas
-- Product integration
-- Use base font size of 1rem (16px)
-- Change font-sizes to rem (a11y)
-
-Current scale: [GitLab UI](https://gitlab-org.gitlab.io/gitlab-ui/?path=/story/scss-typescale--default)
-
-Figma WIP: [Component library →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/8eZJjsriZhPMHL7t1PoVJH/%F0%9F%93%99-Component-library?node-id=440%3A0&t=mKm3NIjPzREZn3q7-0)",3
-113627623,2022-08-22 12:23:03.045,Inter typeface exploration,"### Goal
-
-Make Inter the new default font in GitLab UI & the product.
-
-#### Steps
-- Explore the use of Inter
-- Variable font
-- How we can roll this out
-- Possible performance impacts
-- Language support (i18n)
-- Fallbacks
-
-### Inter
-
-
-
-### Figma Test
-
-[View branch in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/HIA8tpxKnRBR7bFP901AsS/%F0%9F%93%99-Component-library?node-id=440%3A0)
-
-### Product Test
-
-| Inter | system-ui in Mac OS (SF Pro) |
-| ------ | ------ |
-|  |  |",2
-113520415,2022-08-19 10:44:19.333,Revisit the terminology for the filter component parts and guidelines,,2
-113461996,2022-08-18 11:33:17.107,Typography exploration,"Meta issue to explore options regarding typography.
-
-So far @jeldergl & I discussed to explore:
-
-- Switching to Inter
-- Make use of variable font
-- Tweaking/Improving/Streamlining our Typo scales
-- Product integration plan/roadmap
-- Considering an open source monospace typeface to pair with Inter",5
-113287316,2022-08-15 12:26:14.124,Define pattern for adding items to a list,"### Background
-
-Based on [the discussion](https://gitlab.com/gitlab-org/gitlab/-/issues/368138#note_1037362165) with @mle, the improvement could be a community improvement.
-
-So far, we only know that this Region exists in ""Settings"" and ""Security Policy"" if anyone knows where else we are using it, feel free to add.
-
-cc: @gitlab-com/gitlab-ux/designers, Any suggestions or you notice the change won't work in certain area?
-
-### Change Proposal
-
-",3
-112728442,2022-08-03 13:35:05.333,Typography > Note smallest recommended font size,"## Purpose
-
-Some instances of type are showing up that are smaller than the 12px allowed by the current type scales (UI type scale). 12px is a good minimum size and should be used in limited capacity for short meta-like copy and actions. There is no minimum mentioned in Pajamas (although it's implied by the type scale styles), and it'd be helpful to document.
-
-There is subjectivity when it comes to font size and preference, but that's all the more reason to set a baseline and guidance. For example, browsers handle antialiasing differently and rendering ""quality"" will vary. GitLab makes use of system fonts, and some, like Helvetica, have tighter spacing and less character definition so that text is harder to read at small sizes. One user will not have the same eyesight as the next, so setting a minimum can also help remove subjectivity and preference for what should be the minimum size.
-
-If content is worth displaying, then it should be worth displaying legibly.
-
-### Considerations
-
-- On mobile, if the font size of an input is not at least 16px, then input will be scaled up (at least in Safari).
-- Typeface, font weight, color, line-height, measure, and style can all impact legibility.
-- While WCAG doesn't prescribe a minimum font size, it does address contrast for type
-- Pixels are referenced as the unit in this issue, but in code relative units should be used so that a user can scale the type in browser (using pixels prevents this). If a browser's default size is 16px (1rem), then 12px = 0.75rem.
-- Screen resolution will impact legibility.
-
-| **Helvetica, Firefox** | **Helvetica, Firefox, standard resolution** | **San Francisco, Firefox** |
-| ------ | ------ | ------ |
-|  |  |  |
-
-### Resources & reference
-
-- Explore different type sizes and fonts in [CodePen](https://codepen.io/lostsatellites/pen/BarrNoE).
-- https://stephaniewalter.design/blog/what-minimum-font-size-for-a-high-density-data-web-app-do-you-suggest/
-- https://css-tricks.com/accessible-font-sizing-explained/",1
-112626672,2022-08-01 22:30:42.059,GitLab UI stories don't load,"GitLab UI stories seem to be unable to load in some cases. Loading a page that contains stories directly seems to result in the viewers remaining blank.
-
-Stories generally load properly when navigating to a page with stories from within the app although that doesn't seem to be consistently reproducible.
-
-/cc @jeldergl @danmh",2
-112625838,2022-08-01 21:55:19.462,"FY23 Q3 Foundations KR3: Identify opportunities to increase product designer efficiency in Figma. For example, component structure, libraries, internal plugins, etc","## Purpose
-
-See [epic description](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/12).
-
-## Steps
-
-- [ ] Conduct a survey or host a synchronous brainstorming session to explore potential opportunities and workflows that would increase product designer efficiency in Figma.
-- [ ] Identify top 2–3 items that would be the most helpful at this point in time.
-- [ ] Create a roadmap for each item.
-
----
-
-## Retrospection
-
-### Good
-* Some ideas were uncovered during the IA work.
-
-### Bad
-* The IA effort took too long and I didn't get to this.
-
-### Try
-* Breaking down even smaller.",5
-111819368,2022-07-18 23:54:47.955,Rename foundations-color-palette component to color-palette,"The following discussion from !2970 should be addressed:
-
-- [ ] @pgascouvaillancourt started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2970#note_1025851626): (+1 comment)
-
- > **note:** I forgot to give this component a more generic name during the initial implementation. Given that it works in both pages that render color palettes, we can probably rename this to simply `color-palette`. I will do that in a follow-up.",1
-110979806,2022-06-30 17:37:30.725,Abstract color palettes out into a reusable Vue component,"The following discussion from !2910 should be addressed:
-
-- [ ] @pgascouvaillancourt started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2910#note_1010952473): (+2 comments)
-
- > **thought:** There's a lot of duplicated code in this file. Now that we can use Vue components inside Markdown, we should probably think of a way to abstract the color palettes into a reusable component to clean this up a bit.",2
-110887730,2022-06-29 10:12:21.990,Figma > Icon fill issues,"## Description
-
-
-
-Settings icon is behaving like its styled with strokes, rather than fills. This causes some bugs where we rely on fills for overrides — icon dropdown button shown.
-
-
-
-I tried to fix it, but I couldn’t work out how to do it without expanding the strokes — which would be destructive. The usual boolean group tricks don’t seem to be working here.
-
-@nickleonard :
-
-> I've noticed `check` does this as well;
-
-
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/pEkDaidkvHeHVdnmYp6stC/Icon-fix-test?node-id=2%3A2)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [ ] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [ ] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [ ] Update the link to the working file under the **Figma link** section below.
-1. [ ] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [ ] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [ ] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [ ] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [ ] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [ ] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [ ] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [ ] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [ ] From the dropdown to the right of the file name, select ""Request review"".
-1. [ ] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [ ] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [ ] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [ ] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-110504223,2022-06-21 19:32:54.884,"FY23 Q3 Foundations KR2: Gap analysis that determines what areas of Pajamas are missing or needing further refinement, and what the potential impact is","## Purpose
-
-See [epic description](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/12).
-
-## Steps
-
-- [ ] Conduct an internal survey to better understand what perceived gaps are.
-- [ ] Triage open issues to determine what topics and items are most commonly discussed.
- - [ ] Create sub-epics or new issues to organize by theme.
-- [ ] Identify gaps in Pajamas design language. These are the areas that need clarified in order for anyone to have confidence and continuity when building an experience using the design system. For example, I know what component A does, but do I know how to use it with component B, or in a scenario where multiple components exist?
-- [ ] Make proposals to close gaps.
-
----
-
-## Retrospection
-
-### Good
-* Some ideas were uncovered during the IA work.
-
-### Bad
-* The IA effort took too long and I didn't get to this.
-
-### Try
-* Breaking down even smaller.",3
-110504217,2022-06-21 19:32:37.166,Pajamas > Definitions,"- Evaluate existing definitions found at https://design.gitlab.com/get-started/structure with a primary focus on: Foundations, Components, Regions, and Objects.
-- Update definitions and create new ones for sections considered in the [IA exercise](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1378).
-
-[Working file in Figma →](https://www.figma.com/file/qYQOk3DhrswWIsRnoUTJ6J/%231378-Pajamas-IA-JE?node-id=0%3A1)",3
-110504207,2022-06-21 19:32:21.456,FY23 Q3 Foundations KR1: Updated Pajamas IA that takes into account new and updated definitions and organization,"## Purpose
-
-See [epic description](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/12).
-
-## Steps
-
-- [x] Evaluate existing IA to determine opportunities for improvement.
-- [x] Evaluate existing definitions found at https://design.gitlab.com/get-started/structure with a primary focus on: Foundations, Components, Regions, and Objects.
-- [x] Propose definition updates and work through internal discussion.
-- [x] Test updated definitions internally to make sure categories and meaning are clear.
-- [x] Update IA and structure by incorporating definitions and other content organization changes.
-
-## Before / after
-
-Definitions
-
-### Definitions
-
-| | **Before** | **After** |
-| ------ | ------ | ------ |
-| **Foundations** | Foundations represent perceptual patterns. These are less tangible aspects of the design system. Together they create a certain aesthetic for the product. For example, colors, typography, and icons. | Foundational items communicate the opinionated way in which basic visual design attributes, elements, and concepts come together to create a distinct GitLab personality that’s expressed in the UI. For example, color, typography, and iconography. |
-| **Components** | A small design primitive. Components build upon the design foundations (typography, spacing, motion, colors, iconography, etc.) and are the reusable building blocks of the interface. For example, buttons, tabs, and input fields. | A component is a UI element that serves a singular purpose or function. Two or more simple components can combine to form a composite component that still has a single function. For example, an avatar, button, or combobox. |
-| **Regions** | Regions are areas formed by combining multiple components, creating a layout section that can be reused across various pages. For example, the comments and activity feed in issues or merge requests. | _Deprecated_ |
-| **Patterns** | _N/A_ | A pattern combines components and/or content elements into a repeatable, consistent group that has a shared purpose, content association, or both. For example, filtering, forms, or navigation. |
-| **Page templates** | _N/A_ | A template prescribes layout and behavior for a page or common content layout. For example, an issuable, settings, or search results. |
-| **Objects** | Objects capture and organize data as a single source of truth around specific tasks and user interactions. Objects are described in terms of attributes (what they contain), functions (what they do), and relationships (what they interact with). When documented as a conceptual model, objects help understand how the product works and fits together on a system level, detached from the constraints of the user interface. An effective object model tightly aligns our user's mental model with the product's data model. For example, issue, group, and merge request. | An object is a conceptual building block or concept that defines how we think about something independent of its visual representation or interaction model. For example, a job, merge request, or repository. |
-
-
-Information Architecture (IA)
-
-### IA
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-|  |  |
-
-
-
-[ Working file in Figma →](https://www.figma.com/file/qYQOk3DhrswWIsRnoUTJ6J/%231378-Pajamas-IA-JE?node-id=0%3A1)
-
----
-
-## Retrospection
-
-### Good
-* The IA and navigation are being updated and there were some good insights learned.
-
-### Bad
-* This effort took so long that the other KRs didn't get worked on.
-
-### Try
-* Breaking down even smaller.",8
-110282801,2022-06-17 09:44:52.650,Pajamas UI Kit > Form component: Update disabled state update (a11y),"## Description
-
-Disabled state of form items does currently not pass ~accessibility in terms of minimum contrast.\
-This updates the disabled state of the component to pass ~accessibility
-
-### Proposal
-- Change background color from `#fafafa` -> `$gray-10` (`#f5f5f5`)
-- Update Label from `$gray-400` to `$gray-500` for passing contrast (5.28:1)
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-|  |  |
-
-### Figma file
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/9wDCmYQtWqbclCzhE6k2TJ/Component-library?node-id=49840%3A75722)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [x] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-110124885,2022-06-14 23:01:49.627,"Draft: Pajamas scaffolding, structure, and ops","## Purpose
-
-Pajamas provides foundational styles and element, component guidelines, abstracted objects, and UX content, but it's less clear on how to assemble all of these disparate parts. It's these middle guiding layers of the design system that need built out to provide more visual design direction and UI consistency when it comes to implementation.
-
-At the same time, Pajamas needs a common vernacular with agreed upon definitions and categorization. For example, terms like ""patterns,"" ""organisms,"" and ""regions"" mean different things to everyone and time spent aligning on meaning stifles additions and system maturity. A large part of the initial effort will be to refine the GitLab design language and provide the consistent groundwork that efforts like ""unboxing"" and ""beautification"" — and future ones like them — need to stand on. Pajamas is not just _what_, but _how_, and this is what it means to have a design language and not just a design system.
-
-## Phases
-
-1. **Pajamas scaffolding** (%""15.2"")
- - Definitions
- - Website / design system IA and content mapping
- - Gap analysis:
- - Gaps in Pajamas design language
- - Gaps between Pajamas and product
-2. **Pajamas structure** (TBD)
- - Website updates: Implement IA changes
- - SSoT: What would it take to make the Pajamas site the go-to?
-3. **PajamasOps** (TBD)
- - Storybook: Playground, features, robust layouts, accessibility testing
- - Figma: Internal plugins, designer efficiency
- - Triage and contributions
- - Prioritization
-
-## Outcomes
-
-- Consistency in design execution and user experience
-- Shared design language
-- More informed decisions and contribution
-- Pajamas → Product planning and prioritization
-
-## Considerations
-
-- Pajamas documentation should be prescriptive when necessary, and guiding when not. The aim is not to have a draconian system, but one that provides meaningful constraints to foster collaboration, provide clear and informed guidance, and inspire new possibilities.
-- Refining the design language gives space for efforts like tokenizing and theming to have a meaningful place.
-- Gap analysis helps to define not only what areas need building out, but also the size and impact of gaps between Pajamas and the product. For example, typography is foundational, but not consumed by the product.
-
-## Resources and reference
-
-- [IBM Design Language](https://www.ibm.com/design/language/)
-- [Visual Design Language: The Building Blocks Of Design](https://www.smashingmagazine.com/2020/03/visual-design-language-building-blocks/)",5
-110053010,2022-06-13 21:07:54.979,Illustration > Add XS grid size,"## Purpose
-
-A new extra small (XS) grid is being added to provide a size that illustration elements can be created at when they're used alongside other UI or to comprise part of a larger design.
-
-For example, in https://gitlab.com/gitlab-org/gitlab-svgs/-/merge_requests/794 a ""bidirectional-xs"" illustration is being added to connect two logos. Because of our third-party trademark policy we didn't want to add this to one of the logos or combine them. The 72px grid here would've been too large in relation to the logos and placed emphasis in the wrong place.
-
-36px was chosen instead of 32px (and base 8) in order to follow the illustration pattern where each size increases at 2x.",1
-109899028,2022-06-10 08:01:19.741,Color > Adjust $gray-10 from #fafafa to #f5f5f5,"## Description
-
-This is a follow-up to https://gitlab.com/gitlab-org/gitlab/-/merge_requests/87817 & https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89533.
-
-This is a proposal to adjust the `$gray-10` we have defined in the Pajamas Design System to a bit darker nuance.
-FYI: In the product we use a `$gray-normal` which is actally using the same HEX value as this proposed darker nuance.
-
-In https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/2868 we will update `$gray-10` for GitLab UI.
-
-### Proposal
-
-Let's add the following gray's to GitLab UI:
-
-| $gray10 before | $gray10 after |
-| ------ | ------ |
-| `#fafafa` | `#f5f5f5` |
-
-### Figma file
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/eLtdBEfc42kw2eshsyILwK/Component-library)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Make sure all layers are correctly named and organized.
-1. [ ] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [ ] Ensure component descriptions and external documentation links are clear and accurate.
-1. [ ] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [ ] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [ ] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [ ] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-109573190,2022-06-03 17:12:59.765,Navigation > Document naming conventions,"In the `Menu menu discussion` meeting, it was said that we should document naming conventions for navigation. This issue is to investigate what conventions we may be able to create and then document those in Pajamas.",2
-109572586,2022-06-03 17:06:26.462,Navigation > Cross link nav docs,"In the `Menu menu discussion` meeting, it was said that there are multiple navigation docs that exist outside of Pajamas. We should cross link to these pages so it's easy to find/access. We should also consider consolidating where it makes sense.
-
-On the navigation page, we currently cross link to https://about.gitlab.com/handbook/engineering/ux/navigation/",1
-109510113,2022-06-02 13:44:38.428,Helping users > Update content guideline formatting,"Follow up from https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2857#note_957102484:
-
->1. Make the ""GitLab repository `/doc` directory"" a link to that directory.
->1. Format the Content Guidelines as a list. I noticed it follows the same ""when… do this"" type of pattern from other sections and might be easier to parse each consideration as a separate bullet.",1
-109465890,2022-06-01 19:58:04.689,Dropdowns > Add validation notes,"Per this thread https://gitlab.com/gitlab-org/gitlab-ui/-/issues/1242#note_967906969, we should document that certain dropdowns can have validation, namely the listbox and combobox.",1
-109401960,2022-05-31 18:45:35.428,Clarify in Pajamas whether a successful save should be an alert or a toast,"### Problem to solve
-
-We use an info alert on the user settings page to confirm a change, but elsewhere (e.g. the Vulnerability Report), after a successful bulk action, we use a toast notification to confirm the change has been made.
-
-On the [alerts](https://design.gitlab.com/components/alert/#when-to-use) page, Pajamas says:
-> Reaffirm to the user that a prior action, likely in a different location or context, has been successful.
-
-""When to use"" on the [toast](https://design.gitlab.com/components/toast/#when-to-use) page, on the other hand, says:
-> Provide a contextual message based on a user's action in the same view the action took place.
-
-### Proposal
-
-With all the types of alerts we can have in one area at one time (error, warning, etc) in some places, especially the security tab of the pipeline page (see designs in https://gitlab.com/gitlab-org/gitlab/-/issues/352880#note_961677263), we should use toast notifications to confirm a saved change.
-
-Either way, we should update the Pajamas docs accordingly (toast, alert, and [Instant Feedback](https://design.gitlab.com/product-foundations/saving-and-feedback#instant-feedback)) to be more clear which is the suggested pattern.",3
-109024003,2022-05-24 09:10:30.482,Update the sticky component text color to match the background color,"## Description
-
-Update the sticky component text color to match the background color. :sparkles:
-
-| Before | After|
-| ------ | ------ |
-|  |  |
-
-
-
-
-
-### Figma file
-
-
-
-[❖ View working branch in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/wnc5x3SEy35JfUMIbtrupv/Component-library?node-id=1663%3A0)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [-] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-108985322,2022-05-23 15:14:02.446,UI Kit > Fix label variant switch,"## Description
-
-Updated label component to make use of new component properties and added missing states to it.
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-### Figma file
-
-[❖ View working file in Figma →](https://www.figma.com/file/tWdQ8eIy7Br3Uk3qSIWOkf/)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [ ] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [ ] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-108779154,2022-05-19 03:11:36.579,UI kit > Refactor banner,"## Description
-
-Refactoring the banner component in Figma in light of recent app updates.
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-|  |  |
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/jHZaeQQxK6D21f9lrjfj3c/Component-library?node-id=425%3A4)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [-] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-108778498,2022-05-19 02:41:04.304,UI kit > Refactor popover,"## Description
-
-Refactoring the popover component in Figma in light of recent app updates.
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |
-|  |  |
-
-### Figma file
-
-
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/UrBmc6IhZN2zWQCz3HoitL/Component-library)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [-] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-108700135,2022-05-17 18:53:48.379,"Pajamas Migration Day: June 10, 2022","As part of our ongoing [component migration push](https://gitlab-org.gitlab.io/frontend/epic-burndown-charts/fy23-q1/), we are hosting another Pajamas Migration Day!
-
-- **When:** June 10, 2022
-- **Who:** Everyone! FE, BE, Designers, Product, etc. Everyone is encouraged to contribute.
-- **Where:** Your very own home or work space, but also join the `#pajamas_migration_day` slack channel to hang out and chat with fellow contributors!
-- **Why:** We want to encourage a day of migrating legacy components / css to use Pajamas!
-- **Bonus:** If you contribute three merge requests on Pajamas Migration Day, you can expense a meal for up to $25 USD! Please use the ~""Pajamas Migration Day"" label on your MRs to be eligible. In Expensify, use the `Meals Company Provided (Non-Client related)` category.
-
-**Need help?** Ping any member of the [Foundations team](https://about.gitlab.com/company/team/?department=ecosystem-foundations-team) for support or help throughout the day. We are here to assist!
-
-## How to contribute
-
-- ~~[Migrate a few angle icons to chevrons →](https://gitlab.com/groups/gitlab-org/-/epics/8087)~~ All assigned
-- Or if you like buttons more than chevrons :see_no_evil: - you can pick one of the [Haml/Ruby button to Pajamas::ButtonComponent migrations](https://gitlab.com/groups/gitlab-org/-/epics/8153)
-- ~~There are also a couple of [""banners"" to migrate to `Pajamas::BannerComponent`](https://gitlab.com/groups/gitlab-org/-/epics/8076) ViewComponent.~~ All assigned
-- Treat migration day like a scavenger hunt! Review the product and find components/legacy CSS and update it to align with Pajamas!
-- Pick up any issue that that is [ready for development](https://gitlab.com/gitlab-org/gitlab/-/issues/?sort=created_date&state=opened&label_name%5B%5D=pajamas%3A%3Aintegrate&label_name%5B%5D=OKR&assignee_id=None&first_page_size=20).
-
-There does not need to be a specific issue open to contribute! Starting with MRs that migrate legacy code is a great way to contribute to the effort.
-
-**Reminder:** Please add the ~""Pajamas Migration Day"" label to your MRs, as well as the specific component label that relates to your change (for example: ~""component:alert"")",1
-108699933,2022-05-17 18:47:40.487,Consistent dast_environment_deploy job failure in main branch,"Our pipelines are reliably failing in the `dast_environment_deploy` job with the following error message:
-
-> Error: release dast-default failed, and has been uninstalled due to atomic being set: Ingress.extensions ""dast-default-auto-deploy"" is invalid: annotations.kubernetes.io/ingress.class: Invalid value: ""nginx"": can not be set when the class field is also set
-
-Not sure who to ping regarding this issue. It looks like the [Jobs/DAST-Default-Branch-Deploy.gitlab-ci.yml](https://gitlab.com/gitlab-org/gitlab-foss/blob/master/lib/gitlab/ci/templates/Jobs/DAST-Default-Branch-Deploy.gitlab-ci.yml) template was updated recently, perhaps this is related?
-
-https://gitlab.com/gitlab-org/gitlab/-/commit/a91bd39f2c
-
-/cc @hfyngvason @jeldergl",1
-108680374,2022-05-17 12:38:53.806,Dropdown > Reconsider component naming,"## Purpose
-
-Discuss renaming the current **listbox** component while simplifying the dropdown variants.
-
-In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2832 the dropdown component naming was discussed, specifically in regards to the listbox. A `listbox` itself can be part of a disclosure or a `combobox`, but at the moment we're identifying it as its own component that includes the trigger button to reveal it.
-
-It's possible we could reduce the number of documented dropdown variants by treating the listbox as a base component used in composite components.
-
-For example:
-
-- **Disclosure widget**:
- - Button that opens panel of links or a mix of links and actions (buttons).
- - Button that opens a `listbox` containing options (`role=""option""`).
-- **Combobox**:
- - Text input that opens a `listbox` containing options (`role=""option""`).
-- **Menu**:
- - Button that opens a panel of JavaScript app-like actions.
-
-### Comments from the original MR
-
->This definition makes me wonder whether `GlListbox` is correctly named, since it implements the button *and* listbox … Maybe whether or not this matters depends on whether we'd ever want to implement a ""bare"" listbox that's always visible and not just in a popup.
-
->We could name it`GlCollapsibleListbox` as it is named in [the specs example](https://www.w3.org/TR/wai-aria-practices-1.1/examples/listbox/listbox-collapsible.html).",2
-108306864,2022-05-10 12:19:36.328,Improve disabled & focus states of Checkboxes/Radios,"The current disabled state is quite inconsistant with other form elements and has a weak contrast.
-In addition we should update the component to also allow other states as focus & disabled in instances.
-
-Feature branch: https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/DGZF5tMtAdIHpX0oKK7fLn/Component-library?node-id=425%3A10
-
-| Before | After |
-| ------ | ------ |
-|  |  |",1
-108072847,2022-05-05 11:28:18.294,Figma > File uploader: Align file uploader with updates from Gitlab UI,"## Description
-
-The file uploader dashed outline has a weak contrast. Also the indication when dropping files could be improved.
-
-### Proposal
-
-| State | Before | After |
-| ------ | ------ | ------ |
-| Default |  |  |
-| Drag |  |  |
-| Focus |  |  |
-
-### Figma file
-
-[❖ View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/laimESW8ZnHkoAdexjX2UB/%F0%9F%93%99-Component-library?t=BEXsPzdk4w9xJ71g-0)
-
-## Checklist
-
-Make sure the following are completed before closing the issue:
-
-### Assignee tasks:
-
-Getting started:
-
-1. [x] Title the issue using this structure ""Figma > [Component name] - [Description]"". For example, Figma > Badges - Fix icon override bug.
-1. [x] Add the relevant [component label](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/labels?subscribed=&search=component%3A). For example ~""component:badge"".
-1. [x] If you’re making updates or breaking changes to an existing component in the [Pajamas UI Kit](https://www.figma.com/community/file/781156790581391771), start with a [branch](https://www.figma.com/best-practices/branching-in-figma/) of the UI kit. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, `#860-table-component-updates-lvanc`.
-1. [x] When applicable, follow our [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] Update the link to the working file under the **Figma link** section below.
-1. [x] If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. For Component library changes, move your file to the [**Component archive**][component-archive] project.
- 1. For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. If you’re a community contributor, please consider [transferring ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-
-
-Prior to review:
-
-The purpose of these tasks is to ensure consistency with the rest of the components and to save time during the review process. When you are finished with your update, please go through the following clean-up tasks in Figma:
-
-1. [x] **Canvas**: Make sure no hidden elements have been accidentally left behind. Use **View > Show Outlines** (⌘ + Y) to reveal invisible objects. Use **View > Zoom to Fit** (Shift + 1) to view all items on the page.
-1. [x] **Components**: Where applicable, make sure all components have updated descriptions and have external documentation links.
-1. [x] **Frames**: Make spacing within and between frames consistent with components found on other pages.
-1. [x] **Layers**: Make sure all your layers are correctly named and the order match visual from left to right. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Variants**: Remove the default dashed purple stroke, border radius, and padding from all variants.
-1. [x] **Variants**: Reorder variants in properties panel to match visual order. In the case of Auto Layout, Figma will determine layer order.
-1. [x] **Comments**: Make sure all comments and discussion are resolved.
-
-If any of these tasks are unclear, see the [Table component](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=47785%3A58915) for reference.
-
-
-
-Requesting a review:
-
-Ask a [Foundations designer][foundations-team] to review your design.
-
-1. [x] Ensure the designer that will be reviewing your file has edit permissions in Figma.
-1. [x] From the dropdown to the right of the file name, select ""Request review"".
-1. [x] Then from the modal window, remember to include a description of the changes being made and select a reviewer from the right hand column.
-1. [ ] Consider [creating a new version](https://help.figma.com/hc/en-us/articles/360038006754-View-a-file-s-version-history#Create_a_new_version) (optional) titled ""Review requested"" in the history which will create a reference point in the file's history.
-
-Once your file is in review, you should see a yellow ""In review"" badge to the right of the file name.
-
-
-
-Post review:
-Once the Reviewer or Maintainer has approved your update, consider the following tasks:
-
-1. [ ] If it’s a new pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [x] When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [x] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-### Reviewer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s design. Specific design questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Make sure all layers are correctly named and organized.
-1. [x] Stress test final component by changing the component's size, editing content, and changing any available variants and properties.
-1. [x] Ensure component descriptions and external documentation links are clear and accurate.
-1. [x] Approve assignee’s design. Let the assigning know that their changes have been approved by mentioning them in this issue.
-1. [x] Assign to a [Figma maintainer][figma-maintainer] for final review (make sure they have edit permissions in Figma).
-1. [x] Ask a [Foundations designer][foundations-team] to review your design (ensure they have edit permissions in Figma).
-
-
-
-### Maintainer tasks:
-
-See tasks:
-
-1. [x] Review and approve assignee’s changes.
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] Merge the branch or add the changes or additions to the
- target file.
- 1. [x] Ensure that all styles and components now belong to the target file.
- 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [x] When applicable, [publish][publishing] any library changes along with a clear commit message.
-
-
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation
-
-",1
-107923187,2022-05-03 12:57:25.153,List > Deprecate list as a component,"In https://gitlab.com/gitlab-org/gitlab-ui/-/issues/1198#note_930969297 it was proposed and validated that **List** should not be a component for these reasons:
-
->We don't create components of other semantic markup elements, like headings, etc., and I don't think we need to here.
-
-As an outcome of this issue, we'll deprecate the current [List](https://design.gitlab.com/components/list) page in Pajamas and determine if any of the content from that page should be repurposed elsewhere.
-
-We should also determine if the ~""component:list"" label should be updated with a deprecation notice or removed. The assumption is removal since there was never a component built in GitLab UI to begin with.",2
-107914223,2022-05-03 09:59:53.771,Create structure diagram for the Form component,"### Description
-
-Create structure diagram for the Form component.
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [ ] Assign the correct component label to this issue.
-1. [ ] Create an MR with the additions or updates needed.
-1. [ ] When applicable, [create an issue using the `Figma update` issue template][pajamas-figma-update-template] to update the component in Figma, and mark it as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template]. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",1
-107905924,2022-05-03 07:52:07.390,Add guidelines for hiding the UI on empty states,"@dmoraBerlin and I have been chatting on Slack about the work we're doing on the empty group page: https://gitlab.com/gitlab-org/gitlab/-/issues/267014 This issue has been open for a while and now we've aligned on showing the main two options that make most sense in an empty group and hiding the UI that is usually on a group page. Daniel then warned me about Taurie's comment on another issue that could be related: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78012#note_923457878
-
-## Proposal
-
-Let's add some guidance to the empty state guidelines, establish that it's ok to hide the UI in some occasions but that it needs to be carefully thought through as there are cases when showing the UI, even if there's seemingly nothing to show still makes sense and offers more value to the user and hence produces a better user experience.",2
-107880281,2022-05-02 15:40:10.198,Content Security Policy (CSP) blocks iFrames on design.gitlab.com,"## Problem to solve
-
-User on LinkedIn reported
-
->>>
-FYI, I noticed that the CSP blocks some iFrames on multiple pages.
->>>
-
-
-
-Created this issue following the contribution guide in https://design.gitlab.com/get-started/contribute
-
-
-## Resources
-
-- LinkedIn comment: https://www.linkedin.com/feed/update/urn:li:activity:6925139998321053697?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A6925139998321053697%2C6926915289175490563%29",1
-107880056,2022-05-02 15:34:13.247,Figma: add icon to component library,"As Figma now supports Emojis in Filenames to be set as Tab Icon, I'd vote
-that we set one for the Pajamas Component library.
-
-This can be very helpful to easier identify the tab of the component library!
-
-### Proposal
-Add the orange book emoji 📙\
-Other Emoji proposals are welcome, too
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-### What's needed
-Change Filename from `Component library` to `📙 Component library`, that's it! :rocket:",1
-107853598,2022-05-02 08:14:58.025,Alert component: make icon optional,"As in https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/2784 (and https://gitlab.com/gitlab-org/gitlab/-/merge_requests/86006 for the HAML version) we introduced the option to hide the icon, this issue will cover the Figma part to show/hide it.
-
-| with Icon | without Icon |
-| ------ | ------ |
-|  |  |
-
-### Figma
-I created a branch with the needed changes to make the icon optional:
-https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/jChRnVS9BonCCiQNlXaFPj/Component-library?node-id=425%3A1",1
-107372004,2022-04-28 09:50:30.636,Figma pages list improvements,"Let's improve the Figma pages list to add some visual hiearchy.
-
-| Before | After |
-| ------ | ------ |
-|  |  |
-
-Branch: https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/nrjAlk336791WXFtpC88w0/Component-library?node-id=3050%3A0",1
-107361787,2022-04-28 07:43:09.236,Dropdown > Consider consistent widths for the dropdown panel and inputs,"## Problem
-
-
-
-Currently we use inconsistent widths for the dropdown inputs and the dropdown panels. The problems I see:
-
-- Often times the panel width doesn't match the dropdown button or input width
-- The dropdown buttons and inputs are sometimes too long for the content
-
-| The dropdown could match the input in width. | The dropdown could match the dropdown button in width. |
-| ------ | ------ |
-| |  |
-
-| Example in the ""new MR"" page with matching input and dropdown panel width |
-| ------ |
-|  |
-
-## Proposal
-
-I wonder if having set input field widths like `sm` `md` `lg` and `xl` would cover most cases in the product. If we already have fixed sizes for the dropdown button, input, and the dropdown panels, can we make the sizes match so the panel width can be same as the input in most cases?
-
-The width of the dropdown button or input will be selected based on the average expected input string length, and the dropdown width should match the button/input width, except when the input is shorter than the dropdown panel min width.
-
-It'd make the input much more consistent visually.
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [ ] Assign the correct component label to this issue.
-1. [ ] Create an MR with the additions or updates needed.
-1. [ ] When applicable, [create an issue using the `Figma update` issue template][pajamas-figma-update-template] to update the component in Figma, and mark it as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template]. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
-1. [ ] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting.
-1. [ ] 🎉 Congrats, you made it! You can now close this issue.
-
-
-
-[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new
-[component-lifecycle]: https://design.gitlab.com/get-started/lifecycle
-[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",2
-107333098,2022-04-27 21:31:33.210,Update homepage banner,"## Purpose
-
-Update the Pajamas homepage to incorporate elements from the brand update and to remove elements from the background image that could become out of date (also, this will scale better than the current image that gets squished).
-
-[View Figma working file →](https://www.figma.com/file/5ymbd6NElkEPD027vK570d/%231326-Pajamas-banner-JE?node-id=4%3A20)
-
-| **Before** | **After** |
-| ------ | ------ |
-|  |  |",1
-107241908,2022-04-26 19:34:21.883,VPAT > Introduce VPAT 2.4 WCAG template,"## Purpose
-
-GitLab currently uses the [VPAT 2.4 508 template](https://www.itic.org/dotAsset/7d1524dc-e602-47be-8276-ce32bdd58d6c.doc) that uses WCAG 2.0 Level AA Success Criteria as a reference. This doesn't satisfy the needs of those wanting to know where GitLab stands with WCAG 2.1, which is the latest release (WCAG 2.2 is still in draft). For that, there's a separate [VPAT 2.4 WCAG](https://www.itic.org/dotAsset/7edcd54d-c6a6-4649-8375-4a0f0c68eff2.doc) template that we can introduce. For a list of all VPAT templates, visit https://www.itic.org/policy/accessibility/vpat.
-
-### Process
-
-- Update navigation in Pajamas to create a ""GitLab Accessibility Conformance Report"" dropdown that reveals two options:
- - VPAT 2.4 508
- - VPAT 2.4 WCAG
-- Update the current ""GitLab Accessibility Conformance Report"" page title to ""VPAT 2.4 508""
-- Add a new ""VPAT 2.4 WCAG"" page
- - Copy the WCAG 2.0 2.0 data from the VPAT 2.4 508 page into this page
- - Complete an evaluation that adds conformance findings for the [success criteria added in WCAG 2.1](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/)
-- Clarify VPAT and WCAG level on the [Statement of Compliance](https://design.gitlab.com/accessibility/a11y) page",3
-106528622,2022-04-12 13:29:27.580,Migrate to embedded stories in components/tooltip.md,"Migrate away from legacy examples to embedded stories in `components/tooltip.md`
-
-- [ ] Migrated the `vueComponents` property to `stories` in the frontmatter.
-- [ ] Migrated `` components to ``.
-- [ ] Removed the associated examples from the examples/ directory.",1
-106528619,2022-04-12 13:29:25.809,Migrate to embedded stories in components/sorting.md,"Migrate away from legacy examples to embedded stories in `components/sorting.md`
-
-- [ ] Migrated the `vueComponents` property to `stories` in the frontmatter.
-- [ ] Migrated `` components to ``.
-- [ ] Removed the associated examples from the examples/ directory.",1
-106528613,2022-04-12 13:29:22.922,Migrate to embedded stories in components/infinite-scroll.md,"Migrate away from legacy examples to embedded stories in `components/infinite-scroll.md`
-
-- [ ] Migrated the `vueComponents` property to `stories` in the frontmatter.
-- [ ] Migrated `` components to ``.
-- [ ] Removed the associated examples from the examples/ directory.",2
-106528611,2022-04-12 13:29:21.088,Migrate to embedded stories in components/spinner.md,"Migrate away from legacy examples to embedded stories in `components/spinner.md`
-
-- [ ] Migrated the `vueComponents` property to `stories` in the frontmatter.
-- [ ] Migrated `` components to ``.
-- [ ] Removed the associated examples from the examples/ directory.",1
-106190995,2022-04-06 16:34:16.384,Illustration library > Update Figma assets to align with brand,"Update the [Illustration library](https://www.figma.com/file/1ui9w228X0S5WxaD0SRdIA/Illustration-library?node-id=0%3A1) in Figma to align with updates in https://gitlab.com/groups/gitlab-com/marketing/corporate_marketing/-/epics/201 and https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1288.
-
-Updates will have to happen to:
-
-- Styles
-- Grid
-- Components
-- Other?
-
-[View working file in Figma →](https://www.figma.com/file/1ui9w228X0S5WxaD0SRdIA/branch/tMPk4cKFcvn2A0GAp0M932/Illustration-library?node-id=0%3A1)
-
-Updates to tanuki avatars and specific illustrations in the library will happen based on the results of https://gitlab.com/groups/gitlab-org/-/epics/7847 and will be handled on an individual basis.",8
-106190897,2022-04-06 16:33:52.339,Illustration guidelines > Update to align with brand,"Update https://design.gitlab.com/product-foundations/illustration to align with updates in https://gitlab.com/groups/gitlab-com/marketing/corporate_marketing/-/epics/201.
-
-Adaptations may have to be made to account for:
-
-- Grid (dimensions)
-- Figma
-- Color
-- Light/dark UI
-– etc.",3
-106036928,2022-04-04 14:03:13.058,Text input > Move or remove character counter add-on,"
-
-### Description
-
-In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1283, the proposal is to move the character counter outside of the textarea bounds. Given that a similar character counter exists as an add-on in the text input, this issue is to help determine if the character counter should be moved outside of the input bounds and treated as help text (which it is), or to remove it altogether if it's unused.
-
-**Note**: The character counter add-on doesn't currently exist in GitLab UI.
-
-### Proposal
-
-Two options:
-
-1. Remove the character counter from the text input altogether if there are no use cases to support it.
- - Benefits:
- - No need to have a build effort in GitLab UI.
- - Removing unneeded/unused options.
-1. Move the character-counter outside of the input bounds and treat as help text.
- - Benefits:
- - More room for content within the input bounds.
- - Better UX by providing more helpful feedback than just a single number.
- - More consistency with textarea proposal and use of help text.
- - Simplification of component both in the UI kit, and in code.
- - More accessible by providing meaningful feedback outside of the input bounds.
-
-| Option A | Option B* |
-| ------ | ------ |
-|  |  |
-
-\* Option B could either use a {#/#} pattern or more natural text. Also explored in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1283#proposal.
-
-**Questions**
-
-- Is there anywhere in the product that currently uses a character counter on a text input?
-- Is there a current use case for the character counter that some form of help text wouldn't satisfy?
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/ubxFCR4pADM7ZfMJ7ZvyOU/Component-library?node-id=49840%3A75722)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [ ] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [ ] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [ ] **Maintainer**: Review and approve assignee’s changes.
-1. [ ] **Maintainer**: Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [ ] **Assignee**: If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, please consider [transfering ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] **Assignee**: When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] **Assignee**: When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-105911042,2022-04-01 20:29:38.942,Dropdowns > Determine Pajamas IA to support new variants,"## Purpose
-
-In order to support the new ""dropdown"" components from the work in https://gitlab.com/groups/gitlab-org/-/epics/1059, we should consider how we might update the Pajamas navigation to help make it clear that there's more than one type of what is considered a dropdown. For example, a listbox, menu, or disclosure widget, etc.
-
-## Proposal
-
-Use ""Dropdown"" as a component category and have individual pages underneath for each type of implementation.",1
-105906122,2022-04-01 18:27:07.360,Textarea > Update character counter UX and placement,"
-
-### Description
-
-Reconsider the placement of the character counter text and reconsider how the information can be more clearly conveyed. The current counter shows one number, but doesn't provide any comparison.
-
-As uncovered in https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/2738#note_896569524, the current placement of the counter collides with both text within the textarea and the scrollbar.
-
-### Proposal
-
-- Move the character counter outside of the textarea bounding box.
-- Left align the character counter. This follows other form practices where labels and controls are left aligned and help with scanability.
-- Use either a text explanation of what's happening with the counter, or two values so that the limit is always visible.
-- The character counter is basically help text, so it seems to make sense to treat it as such. Additional help text and any validation messages would be below the character counter.
-- Remove text highlight (adds a lot of development complexity).
-- Only change the color for text when the count has been exceeded. The blue conflicts with text that is linked.
-
-| **Current** | **Option A with {#}/{#}** | **Option B with text** |
-| ------ | ------ | ------ |
-|  |  |  |
-
-#### Accessibility considerations
-
-- Visible feedback should also be available/announced for screen reader users. For example, after a pause in typing the limit status is announced via an `aria-live=""polite""` region.
-- The placement of the counter could be out of view with screen magnification turned on, but form validation should help with any error remediation.
-
-### Figma file
-
-
-
-[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/ubxFCR4pADM7ZfMJ7ZvyOU/Component-library?node-id=49840%3A75722)
-
-### Checklist
-
-Make sure the following are completed before closing the issue:
-
-1. [x] **Assignee**: Design in your working file. When applicable, follow our
- [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [Foundations designer][foundations-team].
-1. [x] **Assignee**: Update the link to the working file in the issue
- description.
-1. [x] **Assignee**: Ask a [Foundations designer][foundations-team]
- to review your design (ensure they have edit permissions in Figma).
-1. [x] **Reviewer**: Review and approve assignee’s design. Specific design
- questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility.
-1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer]
- for final review (make sure they have edit permissions in Figma).
-1. [ ] **Maintainer**: Review and approve assignee’s changes.
-1. [ ] **Maintainer**: Merge the branch or add the changes or additions to the
- target file.
- 1. [ ] Ensure that all styles and components now belong to the target file.
- 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure].
-1. [ ] **Maintainer**: When applicable, [publish][publishing] any library
- changes along with a clear commit message.
-1. [ ] **Assignee**: If work was not done in a branch (a merged branch will automatically be archived), move your working file
- to the shared Figma project:
- 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project.
- 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project.
- 1. [ ] If you’re a community contributor, please consider [transfering ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments.
-1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new
- pattern or a significant change, add an agenda item to the next UX weekly call to inform the team.
-1. [ ] **Assignee**: When applicable, add or update relevant documentation and create an MR with your changes using the `Documentation` MR template. If you do not have the capacity, [create another issue using the `Component documentation` issue template][issue-component-template] so we don't forget about it. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] **Assignee**: When applicable, [create a GitLab UI issue using the `Component` issue template][gitlab-ui-component-template] to build or update the component code. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling.
-1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue.
-
-[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations
-[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components
-[foundations-team]: https://about.gitlab.com/company/team/?department=ecosystem-foundations-team
-[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com
-[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes
-[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure
-[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md
-[component-archive]: https://www.figma.com/files/project/5472112/Component-archive
-[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive
-[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component
-[issue-component-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation",1
-105744407,2022-03-30 10:56:41.008,Badge > 12px and 16px icon Figma variants behave the same way,"# Issue
-
-Following on from the changes in #1280+
-
-Badges with 16px icons retain their icon overrides when changing variation.
-
-Badges with 12px icons do not retain their icon overrides when changing variation.
-
-| Behaviour (16px) | Behaviour (12px) |
-| ------ | ------ |
-|  |  |
-
-# Proposal
-
-Make 12px and 16px icon Figma variants behave the same way.
-
-As discussed in the Figma branch for #1280 there are some tradeoffs to be aware of:
-
-- Lose a 'sensible' default
-
-### [Figma branch for review :eyes:](https://www.figma.com/file/xIqrqxGgcl50I8akiQzfmG/%231281-badge-12px-and-16px-icon-override-parity?node-id=19947%3A350)
-
-Full conversation:
-
-Hey Jeremy Elder Nadia Sotnikova
-
-here's a little bug fix for the 12px icon variants to fix
-- Colour persistence when changing icon
-- Icon persistence when changing variant
-
-This makes the 12px icon behaviour the same as the 16px icon behaviour.
-
-However, it does come with some tradeoffs
-- Lose the 'sensible default' icon for each status
-
-wdyt?
-
-Changes:
-- base components: Rename icon symbol layers
-- base components: Relink icons to icon library
-- variant components: Update to use naming from base component
-- variant components: use the same icon to allow icon change persistence
-
----
-
-Dan MH ""Lose the 'sensible default' icon for each status"" might be a dealbreaker for me. These have specific icon/color relationships that should exist out of the box.
-
----
-
-Jeremy Elder I respect and understand that.
-
-I found this unexpected behaviour when trying to add a badge to the Single Stat - https://www.figma.com/file/17NxNEMa7i28Is8sMetO2H/Data-Visualization?node-id=383%3A72
-
-It is a pretty high friction process in its current form. And the defaults aren't sensible here.
-To clarify — my expectation was for these to follow the same persistence rules as 16px icons.
-
-The good news is, I'm 90% sure there is an alternative way we can set these up:
-- Icon swaps use the right colour
-- Variant (colour) swaps change the icon to the icon defined in the variant.
-
----
-
-Dan MH would you be good with me updating this branch to the latest? It'll include the new tier badge.
-
----
-
-Jeremy Elder I'd prefer to do it so I can remember what the changes were see_no_evil emoji
-
-But only if we think we will proceed with any of these updates?
-
-Otherwise we can just delete the branch
-
----
-
->But only if we think we will proceed with any of these updates?
-
-I think it's a valid proposal if you're 90% sure it can be done!
-Applied changes from main, so it may have reset the icons here.
-
----
-
-To confirm the desired/proposed behaviour:
-
-- 12px icon badges come bundled with an icon
-- Icon changes maintain the correct colour to match the badge pill
-- Changing the colour variant changes the icon to the bundled icon
-
-If I'm tying myself in knots trying to explain I can jump on a quick sync at some point
-
-Ok thats all done, and I think it is an improvement as is. :)
-
-However, for many of my use cases the 'sensible defaults' hinder rather than help — so it would be nice to consider changing this behaviour to match the 16px icons in the future!
-
----
-
-Dan MH after some consideration, I don't know that it's helpful to be as prescriptive here.
-
-I had to circle back and through about the ability for you to extend these for your use case, but then that indeed would mean overriding this use case, but this use case is prescriptive and not universal, which isn't what we're going for here. Follow?
-
-So… I'm up for reworking these to use generic defaults that can be updated at the time of use.
-
-What could be helpful, would be adding out instances of the different color/icon/size associations commonly found. Thoughts?
-
----
-
-Thanks for the continued discussion here Jeremy Elder .
-
-Honestly I do see both sides of it.
-
-My workaround was going to be to create extension of these (and other) symbols that match Optimizes use case and maintain them in an Optimize library.
-
-I don't know what is best for the system and its users. Happy to follow your lead here.
-
-I do think merging as-is would be an improvement, perhaps we could open this conversation wider for the last bit?
-
----
-
-Dan MH Figma is having a tough go at spelling out what the changes are that I'm approving, could you unpack it a little further in the review description when you have a moment?
-
----
-
-Jeremy Elder I've documented it in this issue https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1280
-
-I wasn't expecting this much discussion, otherwise I would have created it sooner :D
-",1
Other explorations
- -| vertical2 - Live Example | vertical2 - Component | -| --- | --- | -||| - -| horizontal Live Example | horizontal - component | -| ------------ | --------- | -|   |  | -| | | - -In the first version of the table component a lot of time was put into creating the multi-line variant which shows no usage. | **Insights:**
The checkbox variant is the second most used. This newer update makes it easier to turn on/off the selectable state for entire rows. | - -Note: Thank you @jeldergl for pulling these metrics from Figma. - - -### Figma file - - - -[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/Wli6qiEaC8rnXfeQiukJHw/Component-library?node-id=425%3A11) - -### References -- https://getbootstrap.com/docs/5.0/content/tables/ -- https://mdbootstrap.com/docs/b4/jquery/tables/sort/ -- https://material.angular.io/components/table/overview#sorting -- https://material.io/components/data-tables#anatomy - -### Demo walkthrough - -- :tv: https://youtu.be/7tEa-qT_MfY ---- - -### Checklist - -Make sure the following are completed before closing the issue: - -1. [x] **Assignee**: Design in your working file. When applicable, follow our - [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team]. -1. [x] **Assignee**: Update the link to the working file in the issue - description. -1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team] - to review your design (ensure they have edit permissions in Figma). -1. [x] **Reviewer**: Review and approve assignee’s design. Specific design - questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility. -1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer] - for final review (make sure they have edit permissions in Figma). -1. [x] **Maintainer**: Review and approve assignee’s changes. -1. [x] **Maintainer**: Merge the branch or add the changes or additions to the - target file. - 1. [ ] Ensure that all styles and components now belong to the target file. - 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure]. -1. [x] **Maintainer**: When applicable, [publish][publishing] any library - changes along with a clear commit message. -1. [x] **Assignee**: If work was not done in a branch (a merged branch will automatically be archived), move your working file - to the shared Figma project: - 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project. - 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project. - 1. [ ] If you’re a community contributor, please consider [transfering ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments. -1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new - pattern or a significant change, add an agenda item to the next UX weekly call to inform the team. -1. [x] **Assignee**: When applicable, [create an MR in this repository][new-gitlab-ui-mr] and apply the ""component-guideline"" template - to create or update the component’s documentation page. If you do not have capacity, [create an issue in this repository using the ""Component documentation"" issue template][pajamas-component-documentation-template]. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one. -1. [x] **Assignee**: When applicable, [create an issue in GitLab UI using the ""Component"" issue template][gitlab-ui-component-template] to build or update the component code. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one. -1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue. - -[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations -[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components -[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team -[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com -[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes -[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure -[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md -[component-archive]: https://www.figma.com/files/project/5472112/Component-archive -[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive -[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component -[pajamas-component-documentation-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation -[new-gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new",2 -84821078,2021-04-07 20:17:15.813,FY22-Q2 Foundations KR2: Create a maintained backlog of Pajamas issues that enables product designers and engineers to easily find issues and contribute => 79%,"[FY22-Q2 UX Department: Foundations SubTeam OKR](https://gitlab.com/groups/gitlab-org/-/epics/5726) - -Objective: Ensure Engineering is able to iteratively contribute to and utilize Pajamas for stage work deliverables - -**KR2: Create a maintained backlog of Pajamas issues that enables product designers and engineers to easily find issues and contribute** - -- [x] Ensure all issues within the Pajamas repo have a workflow label. See our [workflow label board](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/boards/1835632) 336/336 => 100% -- [ ] Ensure all issues within the Pajamas repo have a weight. See [issues without weights](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues?scope=all&state=opened&weight=None) 197/336 => 18% - -533/672 => 79%",13 -82133985,2021-04-01 16:22:35.504,Figma > Form > Add form_input_group," - -### Description - -`form_input_group` was introduced in GitLab UI (https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/2115) which includes a form input that is grouped together with another element, such as a label or button. - -This component is being used on the `new fork` page, see https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53544 - -We don't currently have this component within our UI Kit and the styling in GitLab UI does not match our visual language. - -The purpose of this issue is to get the component within Figma, and then to open up the needed issues in GitLab UI to correct the styling. - -### Figma file - - - -[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/cdUPbjyDRc326Rk6KGyxKw/Component-library) (Branch is archived after merge) - -### Checklist - -Make sure the following are completed before closing the issue: - -1. [x] **Assignee**: Design in your working file. When applicable, follow our - [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team]. -1. [x] **Assignee**: Update the link to the working file in the issue - description. -1. [x] **Assignee**: ~~Ask a [FE/UX Foundations designer][foundations-team]~~ Assigned to Figma trainee - to review your design (ensure they have edit permissions in Figma). -1. [x] **Reviewer**: Review and approve assignee’s design. Specific design - questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility. -1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer] - for final review (make sure they have edit permissions in Figma). -1. [x] **Maintainer**: Review and approve assignee’s changes. -1. [x] **Maintainer**: Add the changes or additions to the target file. For - example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file. - 1. [ ] Ensure that all styles and components now belong to the target file. - 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure]. -1. [x] **Maintainer**: When applicable, [publish][publishing] any library - changes along with a clear commit message. -1. [x] **Assignee**: Move your working file to the shared Figma project: - 1. [x] For Component Library changes, move your file to the [**Component archive**][component-archive] project. - 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project. - 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments. -1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new - pattern or a significant change, add an agenda item to the next UX weekly call to inform the team. -1. [ ] **Assignee**: When applicable, create a merge request in this repository - with the [component-guideline template][component-guideline-template] - to create or update the component’s documentation page. -1. [x] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one. -1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue. - -[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations -[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components -[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team -[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com -[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes -[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure -[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md -[component-archive]: https://www.figma.com/files/project/5472112/Component-archive -[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive -[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",3 -81860969,2021-03-29 16:11:53.212,Include GitLab UI utilities,"The following discussion from !2300 should be addressed: - -- [ ] @markrian started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2300#note_540028499): (+2 comments) - - > **question (non-blocking)**: A quick grep suggests we don't use GitLab UI's utility classes in this repo. Should we?",1 -81418386,2021-03-22 14:45:44.188,Badge > Linked badges > Make examples in Pajamas the SSoT,"## Problem - -Embedded badge examples in Pajamas are different from GitLab UI. Having a SSoT will help accurately complete the badge accessibility audit https://gitlab.com/groups/gitlab-org/-/epics/5664. - -| **Pajamas** | **GitLab UI** | -| ------ | ------ | -|  |  | - -## Solution - -Ensure badge examples align with the [badge design specs](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=425%3A3) and that action badges dont underline text on hover.",2 -81248852,2021-03-19 03:53:26.938,Update guidelines around left menu items," -- [x] Guidelines around what the menu items in the left sidebar - - https://design.gitlab.com/regions/navigation#contextual-navigation - - What should be a primary level item vs secondary - - Updated: https://design.gitlab.com/regions/navigation#left-sidebar - - ⛔️ Should ""Labels"" be allowed to jump between a submenu item to parent level? https://gitlab.com/gitlab-org/gitlab/-/issues/21147#note_525491995 - - We are putting Labels into `Project information` https://gitlab.com/gitlab-org/gitlab/-/issues/329905 -- [x] Landing pages should be the first sub menu item - - https://design.gitlab.com/regions/navigation#product-landing-pages - - -## Draft outline - -### Parent item - -### Submenu items - -- Items in the submenu should help support navigation to the parent JTBD and supporting JTBD -- High level features of the category",3 -81245967,2021-03-19 03:15:30.567,Update documentation for global navigation,"## Proposal - -Relates to this page https://design.gitlab.com/regions/navigation#global-navigation - -- [ ] Update documentation for the consolidated projects/group/more menu -- [ ] Add example of the menus mentioned - -~""Category:Navigation & Settings""",2 -80557737,2021-03-09 13:55:08.340,Update the dropdown component with variants and add missing variants," - -### Description - - - -@lvanc and I noticed that there are some cases are missing in our current dropdown component while adding the filter component. https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/720 - -We can add this to the existing component as variants or/and instances. - -And switch to the variants style structure and make the component more flexible. - -| Icon + Text | Text + Help text | User profile | -| ------ | ------ | ------ | -| |  |  | - -### Figma file - - - -[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/2OhkWPJsIE6FSbaTugAVPw/Component-library?node-id=425%3A14) - -### Checklist - -Make sure the following are completed before closing the issue: - -1. [x] **Assignee**: Design in your working file. When applicable, follow our - [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team]. -1. [x] **Assignee**: Update the link to the working file in the issue - description. -1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team] - to review your design (ensure they have edit permissions in Figma). -1. [x] **Reviewer**: Review and approve assignee’s design. Specific design - questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility. -1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer] - for final review (make sure they have edit permissions in Figma). -1. [ ] **Maintainer**: Review and approve assignee’s changes. -1. [ ] **Maintainer**: Merge the branch or add the changes or additions to the - target file. - 1. [ ] Ensure that all styles and components now belong to the target file. - 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure]. -1. [ ] **Maintainer**: When applicable, [publish][publishing] any library - changes along with a clear commit message. -1. [ ] **Assignee**: Move your working file to the shared Figma project: - 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project. - 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project. - 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments. -1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new - pattern or a significant change, add an agenda item to the next UX weekly call to inform the team. -1. [ ] **Assignee**: When applicable, create a merge request in this repository - with the [component-guideline template][component-guideline-template] - to create or update the component’s documentation page. -1. [ ] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one. -1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue. - -[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations -[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components -[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team -[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com -[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes -[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure -[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md -[component-archive]: https://www.figma.com/files/project/5472112/Component-archive -[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive -[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",2 -80543959,2021-03-09 10:32:29.713,Update segmented control visual style," - -### Description - -create consistent button styles - -| Before | New | -| ------ | --- | -|  |  | - - -#### Visual Design Changes - -- Selected states: remove shadows, used a border to indicate selection -- Hover status: a light grey background $gray-50 - -### Figma file - - - -[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/7FLQ3LnDhj3vI7QnGAkTjn/Component-library) - -### Checklist - -Make sure the following are completed before closing the issue: - -1. [x] **Assignee**: Design in your working file. When applicable, follow our - [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team]. -1. [x] **Assignee**: Update the link to the working file in the issue - description. -1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team] - to review your design (ensure they have edit permissions in Figma). -1. [x] **Reviewer**: Review and approve assignee’s design. Specific design - questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility. -1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer] - for final review (make sure they have edit permissions in Figma). -1. [x] **Maintainer**: Review and approve assignee’s changes. -1. [x] **Maintainer**: Add the changes or additions to the target file. For - example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file. - 1. [x] Ensure that all styles and components now belong to the target file. - 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure]. -1. [x] **Maintainer**: When applicable, [publish][publishing] any library - changes along with a clear commit message. -1. [-] **Assignee**: Move your working file to the shared Figma project: (File automatically archived since it was a branch.) - 1. [-] For Component Library changes, move your file to the [**Component archive**][component-archive] project. - 1. [-] For all other changes, move your file to the [**Misc archive**][misc-archive] project. - 1. [-] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments. -1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new - pattern or a significant change, add an agenda item to the next UX weekly call to inform the team. -1. [x] **Assignee**: When applicable, create a merge request in this repository - with the [component-guideline template][component-guideline-template] - to create or update the component’s documentation page. -1. [x] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one. -1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue. - -[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations -[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components -[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team -[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com -[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes -[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure -[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md -[component-archive]: https://www.figma.com/files/project/5472112/Component-archive -[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive -[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",3 -80101565,2021-03-02 15:01:16.599,Update Figma text input to use variants," - -### Description - - - -Figma introduce variants, it is time to update the text input field - -### Figma file - - - -[View working file in Figma →](https://www.figma.com/file/OU6DPkNlneFHnXwcUILWfl/WIP-Update-input-text-field?node-id=1%3A2) - -### Checklist - -Make sure the following are completed before closing the issue: - -1. [x] **Assignee**: Design in your working file. When applicable, follow our - [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team]. -1. [x] **Assignee**: Update the link to the working file in the issue - description. -1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team] - to review your design (ensure they have edit permissions in Figma). -1. [x] **Reviewer**: Review and approve assignee’s design. Specific design - questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility. -1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer] - for final review (make sure they have edit permissions in Figma). -1. [x] **Maintainer**: Review and approve assignee’s changes. -1. [x] **Maintainer**: Add the changes or additions to the target file. For - example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file. - 1. [x] Ensure that all styles and components now belong to the target file. - 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure]. -1. [x] **Maintainer**: When applicable, [publish][publishing] any library - changes along with a clear commit message. -1. [x] **Assignee**: Move your working file to the shared Figma project: - 1. [x] For Component Library changes, move your file to the [**Component archive**][component-archive] project. - 1. [x] For all other changes, move your file to the [**Misc archive**][misc-archive] project. - 1. [x] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments. -1. [x] **Assignee** (or Maintainer, for community contributions): If it’s a new - pattern or a significant change, add an agenda item to the next UX weekly call to inform the team. -1. [-] **Assignee**: When applicable, create a merge request in this repository - with the [component-guideline template][component-guideline-template] - to create or update the component’s documentation page. -1. [-] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one. -1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue. - -[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations -[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components -[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team -[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com -[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes -[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure -[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md -[component-archive]: https://www.figma.com/files/project/5472112/Component-archive -[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive -[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",4 -79233372,2021-02-17 03:19:08.833,Document tree updates in Pajamas [Tree🌲],"Document any changes to the tree component here to be merged into [Pajamas](https://design.gitlab.com/product-foundations/interaction#drag-and-drop}https://design.gitlab.com/components/tree). - -#### 📌 Merge requests - -* .... - -#### ✨ Overall change highlights - -* ...",3 -86894837,2021-02-12 17:07:47.583,Introduce search to Pajamas,"As part of our [Pajamas engagement survey](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1394), we heard that people would like to be able to search through Pajamas to find exactly the information they need. - -How do we go about introducing search to Pajamas?",3 -78823017,2021-02-10 15:30:54.588,Document drag and drop updates in Pajamas [Drag & drop🤏],"Document any changes to drag & drop here to be merged into [Pajamas](https://design.gitlab.com/product-foundations/interaction#drag-and-drop). - -#### :pushpin: Merge requests -- https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/1941 -- .... - -#### :sparkles: Overall change highlights -- ...",3 -78444893,2021-02-04 16:49:34.972,Create live figma embed for form-group submit button behavior,"Based on my confusion of some documentation, I thought it would be worthwhile to add some visual clarity to what we're explaining, specifically for behaviors.",2 -78193008,2021-02-01 10:22:17.161,Update Figma tooltip component with Variant," - -### Description - - - -I worked a lot recently with a tooltip. I found that the current component is not very easy to use because: - -1. I need to detach it every time because the container doesn't auto grow with the text -1. After detach, I need to resize it and not very easy to keep the spacing manually -1. I need to hide/show arrows in the layers instead of using a variant - -So I updated the tooltip component structure with variants, now it can auto grow, two lines just need to hit enter and use different arrow position can be chosen from variants manual on the right-hand side. Please see the picture below :point_down: or watch this [`video intro`](https://www.loom.com/share/bd509b045e8e41f5ae4eb29fc22fb32f). - - -| Current component | Updated component by using variants | -| --- | --- | -|  | | - - -### Figma file - - - -[View working file in Figma →](https://www.figma.com/file/nmpl8tphpsmcDlMYfiviOS/Tooltip-component-update-Pajama-805?node-id=1%3A2) - -### Checklist - -Make sure the following are completed before closing the issue: - -1. [x] **Assignee**: Design in your working file. When applicable, follow our - [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team]. -1. [x] **Assignee**: Update the link to the working file in the issue - description. -1. [ ] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team] - to review your design (ensure they have edit permissions in Figma). -1. [ ] **Reviewer**: Review and approve assignee’s design. Specific design - questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility. -1. [ ] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer] - for final review (make sure they have edit permissions in Figma). -1. [ ] **Maintainer**: Review and approve assignee’s changes. -1. [ ] **Maintainer**: Add the changes or additions to the target file. For - example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file. - 1. [ ] Ensure that all styles and components now belong to the target file. - 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure]. -1. [ ] **Maintainer**: When applicable, [publish][publishing] any library - changes along with a clear commit message. -1. [ ] **Assignee**: Move your working file to the shared Figma project: - 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project. - 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project. - 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments. -1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new - pattern or a significant change, add an agenda item to the next UX weekly call to inform the team. -1. [ ] **Assignee**: When applicable, create a merge request in this repository - with the [component-guideline template][component-guideline-template] - to create or update the component’s documentation page. -1. [ ] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one. -1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue. - -[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations -[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components -[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team -[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com -[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes -[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure -[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md -[component-archive]: https://www.figma.com/files/project/5472112/Component-archive -[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive -[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",2 -77550425,2021-01-20 14:23:00.232,chore: Point gitlab-ui status links to Storybook,,2 -77176298,2021-01-13 16:46:21.198,Guideline to open help links in new tab or not,"In the [helping users](https://design.gitlab.com/usability/helping-users) section of the pajamas, we make use of two kinds of text links. While it's clear what the text should be, there's no guideline whether that link should open in a new tab or not. - -We do however have some general guidelines about [external links](https://design.gitlab.com/product-foundations/interaction/#links-to-external-resources). - -## More details - -I personally am in favor of the new tab functionality, and this makes sense for GitLab.com where we now redirect all help links to the external site https://docs.gitlab.com. - -For self-managed instances however, the help links still point to the `/help` page of the instance. - -## Accessibility issues - -Best practice for accessibility by default is to use native browser behavior and open in the same window. -Once `target=""_blank""` is used it disables all other browser options, so it’s best to let the user choose. - -## Resources - -- https://css-tricks.com/use-target_blank/ -- Docs guidelines on links https://docs.gitlab.com/ee/development/documentation/#linking-to-help",1 -76702013,2021-01-04 14:19:33.381,Form: multi-column/row of grouped options in forms,"### Background - -This is an issue created based on [another issue](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues). Before we document something we agree on, we want to explore different solution options. - -### Problem - -In some areas, the user needs to set up complicated settings, such as variable sets with some details fine-tuning. Each variables settings is a group, and users need to see them together to have a better overview or comparing different variable groups. - -The design needs to be flexible for desktop and mobile, easy to read and identify the groups. - -| Example 1 | Example 2 | -| --------- | --------- | -|  |  | - - - -### Solution - -| Option 1 - Row grouping | Option 2 - Column grouping | Option 3 -??? | -| --------- | --------- | -------- | -|  |  | | -| | | |",3 -76385293,2020-12-22 13:01:27.956,Examples are sometimes loaded from an incorrect component,"In https://design.gitlab.com/components/accordion/code, the examples are loaded from `GlAccordionItem` instead if `GlAccordion`.",1 -73936334,2020-11-05 19:45:18.779,Content section > Determine how to dedupe documentation with doc styleguide,"# Problem - -There are currently multiple places where we have content guidelines including: - -* Pajamas: [Punctuation](https://design.gitlab.com/content/punctuation), [Terminology](https://design.gitlab.com/content/terminology), [Voice and tone](https://design.gitlab.com/content/voice-tone) -* Docs: [Styleguide](https://docs.gitlab.com/ee/development/documentation/styleguide.html) -* Handbook: [Styleguide](https://about.gitlab.com/handbook/style-guide/), [Markdown](https://about.gitlab.com/handbook/markdown-guide/) - -There is repeated content in all of these sections, making it difficult to know when to go where for what. - -We've started trying to harmonize this content between the different areas, which is resulting in content that is not DRY. For example, see https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26326 and https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2148. - -Tech writing has started to look at both styleguides and align them here: https://gitlab.com/gitlab-org/gitlab-docs/-/issues/636. However, we need to determine the IA in order to ensure that we are not continuing to duplicate content over time. - -# Solution - -Determine how to dedupe content docs in all various locations. This could include: - -- Moving all content docs to one area - - Pros: Everything is in one place, you always know where to go to find what you need. Content isn't duplicated. - - Cons: There are separate use cases for docs and product, so the documentation in this section could be expansive. Good IA would be needed so its easy to find details. -- Keeping documentation docs and product docs separate, with clear cross-linking as needed. - - Pros: Separation of concerns could make it easier to find detailed docs as needed - - Cons: A lot of content overlaps, so it may be difficult to fully dedupe and could mean lots of cross linking and jumping back and forth between sections.",8 -73807957,2020-11-03 14:54:40.845,Move calendar icon in date picker,"Per @cam.x’s great suggestion in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/726#note_432971319, consider moving the calendar icon to the left of the date picker input. - -**Benefits** - -- Aligns with how the search input is handled. -- Provides more room on the right to use the clear × option. - - - -/cc @gitlab-com/gitlab-ux/ux-foundations",2 -72858125,2020-10-16 23:12:12.730,Add lock-solid to GitLab UI Kit for Figma," - -### Description - - - -When switching between  and  there is not enough visual distinction to quickly identify if something is locked or unlocked. - -:new: icon  - -🤚Blocking Merge Request  - https://gitlab.com/gitlab-org/gitlab-svgs/-/merge_requests/632 - -### Figma file - - - -[View working file in Figma →](https://www.figma.com/file/nLyPs9zeRPQUAAmKckfLjM/Icon-lock-solid?node-id=125%3A35) - -### Checklist - -Make sure the following are completed before closing the issue: - -1. [x] **Assignee**: Design in your working file. When applicable, follow our - [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team]. -1. [x] **Assignee**: Update the link to the working file in the issue - description. -1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team] - to review your design (ensure they have edit permissions in Figma). -1. [ ] **Reviewer**: Review and approve assignee’s design. Specific design - questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility. -1. [ ] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer] - for final review (make sure they have edit permissions in Figma). -1. [ ] **Maintainer**: Review and approve assignee’s changes. -1. [ ] **Maintainer**: Add the changes or additions to the target file. For - example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file. - 1. [ ] Ensure that all styles and components now belong to the target file. - 1. [ ] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure]. -1. [ ] **Maintainer**: When applicable, [publish][publishing] any library - changes along with a clear commit message. -1. [x] **Assignee**: Move your working file to the shared Figma project: - 1. [x] For Component Library changes, move your file to the [**Component archive**][component-archive] project. - 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project. - 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments. -1. [ ] **Assignee** (or Maintainer, for community contributions): If it’s a new - pattern or a significant change, add an agenda item to the next UX weekly call to inform the team. -1. [ ] **Assignee**: When applicable, create a merge request in this repository - with the [component-guideline template][component-guideline-template] - to create or update the component’s documentation page. -1. [x] **Assignee**: When applicable, [create an issue in GitLab UI][new-gitlab-ui-issue] to build or update the component code. Mark the new issue as related to this one. -1. [ ] **Assignee**: 🎉 Congrats, you made it! You can now close this issue. - -[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations -[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#building-components -[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team -[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com -[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#publishing-changes -[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/doc/pajamas-ui-kit.md#structure -[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/master/.gitlab/merge_request_templates/component-guideline.md -[component-archive]: https://www.figma.com/files/project/5472112/Component-archive -[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive -[new-gitlab-ui-issue]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new",1 -72834541,2020-10-16 12:41:20.757,UX Foundations > Pajamas OKR exploration,"During a recent conference, Design Systems & DesignOps, one of the self-work times was dedicated to thinking through what OKRs could look like for your design system. We were given about 40 minutes total to complete a list and then discuss in a small group. These were a few that came to mind, and I found it very helpful to think through objectives specific to the system itself. - -Feel free to add your own, and perhaps we can have further exploration on a few of these. All of the below ramp up to a larger objective of making the product more beautiful, performant and accessible for users, while providing clear _foundational_ answers to common questions so that designers can focus on designing and not on rehashing what should be “boring” decisions. A reoccurring phrase from the workshop was “align the easy thing to do with the right thing to do,” which I think aligns with our goal of building foundational things for the team to build on.",1 -72338921,2020-10-07 16:28:24.133,Dropdown component - Standardising on how to clear selection,"## Problem - -- From this discussion: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/43050#note_422606858 -- There doesn't seem to be a standard way to clear the selection from a dropdown -- For example, in Value Stream Management, the following approach was used... - - - -## Proposal - -Standardise on a solution for clearing the selection from a dropdown: -1. Document approach -1. Add functionality at the component-level - -There are a few ways of going about it... - -### When dropdown is open, the Action area for ""clear selection"" - -| Single selection | Multi selection | -| ------ | ------ | -|  |  | - - -### after dropdown closes, the action to ""clear selection"" -| Single selection | Multi selection | -| ------ | ------ | -|| | - - -
Original proposal
--| Dropdown open clear button | Dropdown closed clear button | Top-level selection clears | -| ------ | ------ | ------ | -|  |  |  | -
-👁🗨 View initial concepts
- -| | **Blue highlight** | **Gray highlight** | -| ------ | ------ | ------ | -| **Edge-to-edge checkmark ✓** |  |  | -| **Inset rectangle checkmark ✓** |  |  | -| **Edge-to-edge border ⎮** |  |  | - -🎛 View more examples for comparison
- -| | **Blue highlight** | **Gray highlight** | -| ------ | ------ | ------ | -| **Edge-to-edge checkmark ✓** |  |  | -| **Inset rectangle checkmark ✓** |  |  | -| **Edge-to-edge border ⎮** |  |  | - -Full audit table
- -| Search input field | Filters | -| ------ | ------ | -| Projects  | Issues  | -| Groups  | Members  | -| Explore topics  | Requirements  | -| Milestones  | Merge requests  | -| Projects sub-menu  | Pipelines  | -| Global search  | Global search with filters  | -|Labels  | Test cases  | -|Commits  | Vulnerability report  | -|Branches  | Policies  | -|Tags  | Incidents  | -|cell | Package registry  | -|cell | Container registry  | -|cell | Value stream analytics  | -|cell | Code review  | -|cell | Issue analytics  | -|cell | Merge Request Analytics  | -|cell | To-Do List  | - -- Primary
- Secondary
- Tertiary
**Variants:**
- Confirm
- Default
- Dashed
- Danger
- Link | **Variants:**
- Confirm
- Primary
- Secondary
- Tertiary
- Default
- _Same pattern as Confirm_
- … | - -This would focus on the variants, and then the options for each variant. I think doing away with the category content as-is would be helpful. We can still identify primary, secondary, and tertiary actions, but secondary to variant. We could always take naming further, but a change like this doesn't require component changes as far as I can tell, just how it's presented.",3 -90680025,2021-07-22 12:50:23.019,GFM Typescale > Code span > design,"Create Figma specs for the GitLab Flavored Markdown code span component. - -See parent epic for detailed information about this component. - -- [Documentation markdown - Code span](https://www.figma.com/file/V3HKN83B7rf2T6sseLMrxa/Type-scale---Documentation-Markdown?node-id=909%3A10) -- [Compact markdown - Code span](https://www.figma.com/file/mjAZxHkK95TlQ6L14aNp2M/Type-scale---Compact-Markdown?node-id=862%3A4)",1 -90567168,2021-07-20 15:06:53.560,Add Pajamas Playground to documentation,"### Problem - -While the Pajamas documentation provides extensive examples and code snippets for our components, there is currently no easy way to try our design system without installing GDK or creating a GitPod instance. - -### Proposal - -This issue proposes adding a Pajamas Playground to our documentation (potentially as a simple iframe), to remedy this gap and enable designers & developers to: - -- Quickly try component code directly in the browser -- Test different component props and combinations -- Easily collaborate and generate code snippets for other developers - -**Question for the Foundations Team**: Do you see this as something useful and worth integrating into the docs? - -You can see a working proof of concept at https://dfosco.gitlab.io/pajamas-playground - - - -### Possible Next steps - -The proof of concept above is a very rough prototype, and it can likely break very easily. Possible next steps to integrate this as an official part of our tooling include: - -- Embed playground in a dedicated page of Pajamas docs -- Update code to dynamically import the latest version of _every_ Pajamas component (including new ones) -- Add sharing button to append current code to URL -- see [example on Auth0 docs](https://auth0-cosmos.vercel.app/#/playground) -- General cleanup of the code to meet team standards and reliability",2 -90357136,2021-07-15 20:55:24.985,Pajamas > Move contributing content,"## Problem - -- Recently the **Component lifecycle** content was updated, but it still remains the last item in the menu and could be elevated for more visibility. -- Under the **Contribute** menu heading there is a **Get started** page, but there is already a **Get started** navigation heading above. - -## Solution - -- Move the **Component lifecycle** page under the top **Get started** menu heading. -- Move the **Get started** page under the top **Get started** menu heading and rename the page to ""Contribute."" -- Remove the **Contribute** menu heading. -- Update any Pajamas links to point to the new pages. - -",2 -90289738,2021-07-14 19:19:57.566,Regions > Add merge request reports,"## Purpose - -Add [merge request reports](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=38197%3A204050) to the **Regions** section of Pajamas. The initial content will come from the [Figma file](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/Component-library?node-id=38197%3A204050). This is in preparation of the implementation phase for the MR widgets and having the SSoT in Pajamas.",2 -90287401,2021-07-14 18:11:48.454,"Follow-up from ""feat(Color): Add color theme notes""","The following discussion from !2460 should be addressed: - -- [ ] @jeldergl started a [discussion](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2460#note_625218336): (+6 comments) - - > Note: these changes (and others like it) were brought about by the lint job that runs during a commit. - ---- - -The changes in question was the removal of indentation for HTML within a markdown file. The indentation helps with nesting and understanding the code. Removing it makes the markup harder to read and understand.",1 -89872209,2021-07-07 03:12:00.014,Update Sidebar navigation component," - -### Description - - - -Updating the `Sidebar` component to match the direction of the navigation changes from %""14.0"" - -- Using the gray-900 color instead of having theme color influence the sidebar https://gitlab.com/gitlab-org/gitlab/-/issues/330467 -- Using the name `Infrastructure` instead of `Kubernetes` in instances to reflect https://gitlab.com/gitlab-org/gitlab/-/issues/334011 - -### Figma file - - - -[View working file in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/3wLvv6JyQvhy07Jxkvc630/Component-library?node-id=3050%3A0) `update-sidebar-component` branch - -### Screenshots - -Variants - -| Before | After | -| ------ | ------ | -|  |  | - -Instances - -| Before | After | -| ------ | ------ | -|  |  | - -### Checklist - -Make sure the following are completed before closing the issue: - -1. [x] **Assignee**: Design in your working file. When applicable, follow our - [structure][structure], [building][building], and [annotation][annotation] guidelines. If you have any questions, reach out to a [FE/UX Foundations designer][foundations-team]. -1. [x] **Assignee**: Update the link to the working file in the issue - description. -1. [x] **Assignee**: Ask a [FE/UX Foundations designer][foundations-team] - to review your design (ensure they have edit permissions in Figma). -1. [x] **Reviewer**: Review and approve assignee’s design. Specific design - questions can be addressed with comments in Figma. Comment in this issue when the content is less specific to the design or requires greater visibility. -1. [x] **Reviewer**: Assign to a [Figma maintainer][figma-maintainer] - for final review (make sure they have edit permissions in Figma). -1. [x] **Maintainer**: Review and approve assignee’s changes. -1. [x] **Maintainer**: Add the changes or additions to the target file. For - example, you’d copy a final chart design from the working file and paste into the related location in the Data Visualization file. - 1. [x] Ensure that all styles and components now belong to the target file. - 1. [x] For changes to the **Component Library** file, view the components in the Assets panel to ensure they align with our [asset library structure guidelines][structure]. -1. [x] **Maintainer**: When applicable, [publish][publishing] any library - changes along with a clear commit message. -1. [x] **Assignee**: Move your working file to the shared Figma project: - 1. [ ] For Component Library changes, move your file to the [**Component archive**][component-archive] project. - 1. [ ] For all other changes, move your file to the [**Misc archive**][misc-archive] project. - 1. [ ] If you’re a community contributor, we ask that you [transfer ownership of your draft file](https://help.figma.com/hc/en-us/articles/360040530853) to the maintainer so they can move it to our archive, along with its version history and comments. -1. [-] **Assignee** (or Maintainer, for community contributions): If it’s a new - pattern or a significant change, add an agenda item to the next UX weekly call to inform the team. -1. [-] **Assignee**: When applicable, [create an MR in this repository][new-gitlab-ui-mr] and apply the ""component-guideline"" template - to create or update the component’s documentation page. If you do not have capacity, [create an issue in this repository using the ""Component documentation"" issue template][pajamas-component-documentation-template]. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one. -1. [x] **Assignee**: When applicable, [create an issue in GitLab UI using the ""Component"" issue template][gitlab-ui-component-template] to build or update the component code. Bring the issue to your team planning session for prioritization and scheduling. Mark the new issue as related to this one. -1. [x] **Assignee**: 🎉 Congrats, you made it! You can now close this issue. - -[annotation]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#adding-descriptions-notes-and-annotations -[building]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#building-components -[foundations-team]: https://about.gitlab.com/company/team/?department=fe-ux-foundations-team -[figma-maintainer]: https://about.gitlab.com/handbook/engineering/projects/#design.gitlab.com -[publishing]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#publishing-changes -[structure]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/doc/pajamas-ui-kit.md#structure -[component-guideline-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/.gitlab/merge_request_templates/component-guideline.md -[component-archive]: https://www.figma.com/files/project/5472112/Component-archive -[misc-archive]: https://www.figma.com/files/project/10620392/Misc-archive -[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component -[pajamas-component-documentation-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Component%20documentation -[new-gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new",2 -89563039,2021-06-30 19:40:55.756,Update component markdown template,"### Description - -Update the [example component documentation page template](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/pages/components/template.md) after https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2414 has been merged to reflect template updates. - -### Checklist - -Make sure the following are completed before closing the issue: - -1. [x] Assign the correct component label to this issue. -1. [x] Create an MR with the additions or updates needed. -1. [-] When applicable, [create a new Pajamas issue using the ""Figma update"" issue template][pajamas-figma-update-template] to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one. -1. [-] When applicable, [create an MR in GitLab UI][gitlab-ui-mr] to update the component. If you do not have capacity or are unable to update the component directly, [create a new GitLab UI issue using the ""Component""][gitlab-ui-component-template] issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one. -1. [x] When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting. -1. [x] 🎉 Congrats, you made it! You can now close this issue. - - - -[gitlab-ui-mr]: https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/new -[component-lifecycle]: https://design.gitlab.com/contribute/lifecycle -[pajamas-figma-update-template]: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/new?issuable_template=Figma%20update -[gitlab-ui-component-template]: https://gitlab.com/gitlab-org/gitlab-ui/-/issues/new?issuable_template=Component",1 -89489145,2021-06-29 15:26:55.709,Add bot warning for workflow label and weight,"## Purpose - -In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/850 the UX Foundations team is working on adding workflow labels and weights to each issue. When a new issue is created there's no way for the author to know that a workflow label and weight should be added. - -The proposal is to have a bot notify the author to add the workflow label or weight, or to automatically add a label. - ---- - -Message: - -``` -Hi @[AUTHOR], - -Please add a [workflow label](https://about.gitlab.com/handbook/product-development-flow/) and [weight](https://about.gitlab.com/handbook/engineering/ux/ux-designer/#ux-weight-definitions) to your issue. This helps to categorize and locate issues in the future. - -Thanks for your help! :heart: - ---- - -You are welcome to help [improve this comment](LINK). -```",2 -89486695,2021-06-29 14:47:29.804,Evaluate VPAT against GitLab v14.0,"## Purpose - -In https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2434 we're updating the VPAT version to note that no material changes happened between 13.5 (date of current report) and 14.0. [More context](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1031) - -This effort evaluates 14.0 against the current VPAT report, makes any updates, and updates the version and report date in the VPAT.",2 -89416050,2021-06-28 14:55:53.428,Pajamas competitor analysis,"This issue is to discuss the possibility for doing competitor analysis for Pajamas. I think it will be valuable to do a lightweight version of the UX competitor analysis to gain insight into how we can continue to improve Pajamas, by taking a look at some other design systems. - -I think we have the opportunity to do something from scratch, I have heard from multiple designers that the current competitor analysis in UX is too in depth, perhaps we look at developing our own from scratch that's much simpler. - -- [ ] Determine whether doing a competitor analysis is useful - - [ ] Determine how a formal competitor analysis will be structured",1 -88894335,2021-06-17 16:53:34.548,Where should research insights live that impacts Pajamas?,"## Purpose - -In a recent 1:1 I brought up the idea of using the wiki feature in the Pajamas project to house research insights and more conversational reasoning behind decisions that impact components. From each component page we could link to the relevant section of the wiki. - -This brought up the need to address a few questions at a higher level before solutioning: - -- Where should research live and how should it be incorporated into Pajamas (if at all)? -- Is there still an insights repo that could be linked to? - -Currently, in https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2414 as part of the component page template update a new ""Reference"" section is being added with the intent to add links and commentary. - -The component page documentation should be direct, and we don't want to add to the overhead by having research links throughout that might be private or change. So where could we have a SSoT and how should we reference it?",1 -88587817,2021-06-11 16:13:24.805,Tree > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the tree component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587816,2021-06-11 16:13:24.359,Tooltip > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the tooltip component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587815,2021-06-11 16:13:24.058,Token > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the token component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587814,2021-06-11 16:13:23.841,Toggle > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the toggle component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587813,2021-06-11 16:13:23.597,Toast > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the toast component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587811,2021-06-11 16:13:22.914,Tabs > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the tabs component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587809,2021-06-11 16:13:21.965,Table > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the table component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587808,2021-06-11 16:13:21.753,Spinner > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the spinner component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587807,2021-06-11 16:13:21.385,Sorting > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the sorting component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587806,2021-06-11 16:13:21.189,Socks > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the socks component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587805,2021-06-11 16:13:20.977,Skeleton loader > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the skeleton loader component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587804,2021-06-11 16:13:20.775,Segmented control > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the segmented control component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587803,2021-06-11 16:13:20.495,Search > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the search component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -88587802,2021-06-11 16:13:20.292,Radio button > Update docs to utilize new template,"## Background - -As part of https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/541, we worked on a new page template for the `Usage` tab of component pages. - -## Resources - -See the [parent epic](https://gitlab.com/groups/gitlab-org/gitlab-services/-/epics/5) for the new template, as well as a few examples of components that have already been migrated to the new structure. - -## Proposal - -Update the radio button component usage tab to be in alignment with the changes. - -This may involve rewording content in addition to restructuring sections. After pushing up your MR, assign it to another Foundations design member for review.",1 -127230475,2023-04-26 19:42:12.971,UI kit > Clarify heading breakpoints,"## Description - -The breakpoint prefixes for heading styles can be perceived as available size options to be chosen from based on preference rather than sizes that need to be applied at a breakpoint. - -## Solution - -Make the size more verbose and clear by adding ""breakpoint"" and clarifying the range. - -[ View in Figma →](https://www.figma.com/file/qEddyqCrI7kPSBjGmwkZzQ/branch/HHCrSCelPUHKKK0d1QViMT/%F0%9F%93%99-Component-library?t=tGJp4jMMw0kkjMQM-11) - -**Example**: - -| **Before** | **After** | -| ------ | ------ | -| `UI/h1/sm` | `UI/h1/≤md breakpoint` | -| `UI/h1/xl` | `UI/h1/≥xl breakpoint` | -|  |  | - -## Checklist - -Make sure the following are completed before closing the issue: - -### Assignee tasks: - -