Type scale > Integration branch preparation

Context

What is this issue?

Type scale > Integration branch collaboration (#2244 - moved) will require close collaboration between multiple designers on a large effort.

This issue tries to set that effort up for success.

What does that other issue entail?

At a high level: migrating all of the headings in GitLab to use consistent styles. Removing overrides and improving semantics as we go.

In detail: TBD 🫣 working out scope and approach is the goal of this issue.

Issue

Things to be done before starting the type scale integration collaboration:

Design decisions

• Have heading type scales implemented in gitlab-ui #2137 (moved)
• Have heading type scales, the underlying global text size scale, and the reasons, documented in Pajamas gitlab-org/gitlab-services/design.gitlab.com#1527 (closed)
• Determine design approach for deciding on contextual overrides
• Determine system level solutions to common patterns. For example, first heading to top of page, or heading to meta #2246 (comment 1430829993)
• Create help for UX reviewers

Technical approach

• Determine technical approach for applying standard styles (and removing existing overrides)
• Determine technical approach for applying contextual overrides (and removing existing overrides)
• Determine branching strategy. For example, one mega branch, lots of little branches, MRs based on other MRs? #2246 (comment 1425459131)
  • If multiple MRs, create MR template for use in effort
• Create help for technical reviewers

Scope

• Define whats in scope #2246 (comment 1430887375)
• Define whats out of scope #2246 (comment 1430887375)
• Decide how to track progress
• Decide how to distribute work
• Are there existing open issues we can close as part of this effort

Integration branch guide

https://docs.google.com/document/d/1y75XYvGJikp8itvDDxafpBHkuX-MGanYbFj4egDXasI/

Gdoc for collaboration. Move to issue/MR/repo when more stable.

Checklist

• Foundations PDM to approve design approach
• Foundations EM to approve technical approach
• Foundations PM or Sr. Manager of Product Design to approve scope
• Create integration branch MR
  • Add guidelines for applying standard styles
  • Add guidelines for determining and applying contextual overrides
  • Add guidelines for common patterns
  • Add guidelines for branching strategy
  • Add help for reviewers