-
-
Notifications
You must be signed in to change notification settings - Fork 778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Design system heading typography in the code base #1743
Labels
Complexity: Medium
Feature: Design system
milestone: missing
role: front end
Tasks for front end developers
size: 1pt
Can be done in 4-6 hours
To Update !
No update has been provided
Comments
Sihemgourou
added
role: front end
Tasks for front end developers
Complexity: Medium
labels
Jun 15, 2021
Sihemgourou
changed the title
Implement Design system on the code base
Implement Design system in the code base
Jun 15, 2021
daniellex0
changed the title
Implement Design system in the code base
Implement Design system heading typography in the code base
Jun 17, 2021
sayalikotkar
added
the
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
label
Jun 20, 2021
Sihemgourou
added
Feature: Design system
and removed
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
labels
Jun 20, 2021
@Zak234 Please add update
|
2 tasks
62 tasks
This was referenced Aug 10, 2021
Question/clarification: Are these new typography classes meant to only affect the sizes of the "toolkit" page? or should they be set-up to be applied "site wide"? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Complexity: Medium
Feature: Design system
milestone: missing
role: front end
Tasks for front end developers
size: 1pt
Can be done in 4-6 hours
To Update !
No update has been provided
Overview
We need to implement the headings part of the design system as classes in the code base so that our heading sizes are no longer attached to h1/h2/h3 tags etc and can no longer negatively affect the accessibility/hierarchy of the web pages for people using screen readers
Action Items
Resources/Instructions
Figma
The text was updated successfully, but these errors were encountered: