Landmark typography updates #5575
Open
+78
−78
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
❌ Deploy Preview for hpe-theme-preview failed. Why did it fail? →
|
❌ Deploy Preview for unrivaled-bublanina-3a9bae failed. Why did it fail? →
|
✅ Deploy Preview for hpe-design-icons-grommet ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deploy Preview -> Typography
Deploy Preview -> Typography System
What does this PR do?
Relocate and update typography content defined in this Figma file
This update reorganizes the typography content to better follow Diátaxis principles. All explanatory and conceptual guidance—text width best practices, responsive behavior, accessibility rationale, and heading-usage rules—was moved to the Foundations → Typography page. All token values, implementation details, and reference-style information were consolidated under Tokens → Typography system. This separation clarifies what is explanation vs. what is reference, reduces redundancy, and makes the page easier to navigate.
Address Issue 5414
What are the relevant issues?
Where should the reviewer start?