Conversation
**Why**: Toward migration off BassCSS to design system.
anniehirshman-gsa
left a comment
There was a problem hiding this comment.
Thanks for surfacing this! I agree that it'd be good to make these semantic headings even if the large text size changes a little. In fact, I updated the Upload page heading to an h2 in mockups for a design improvement that hasn't been implemented yet (Figma, LG-5196).
The only trick is that with the current font set, h2s are serifs and it would be preferable to keep them sans. Do you have a good suggestion for a temporary fix for that?
Yeah, we can use the For reference, this is what it looks like with that change:
I can go ahead and make the change if it looks alright to you? I think it does match what's in the current Figma design, rendering at |
LGTM thanks! 👍 |


Why: Toward migration off BassCSS to design system.
The
font-sans-lgdesign system utility class provides a similar font size styling effect (1.5remwithh1vs.1.46remwithfont-sans-lg). In the future, we may consider avoiding these classes altogether, toward more semantic elements such as headings, or componentizing specific usage such as process lists (LG-4791).Open Questions:
1.25rem, which matches neitherh1norfont-sans-lg. Does that font size correspond to anything meaningful (component, etc)? Should it be customized to match the design, or should the design be updated to use the design system font size token?(cc @anniehirshman-gsa)
Screenshots: