Open halocline opened 1 year ago
Some quick and initial thoughts on this..
Interested to understand how this would work with the new Figma variables. Or if and how this could be applied with variables.
Some concerns..
We designers would still have to update each instance as we would in the centralized location if any of the Heading sizes were to be needed to change.
This can create confusions for designers when looking for Heading sizes since we have all of our text styles, including Headings and Anchors in a centralized location. If we componentize, designers would have to search for component in assets. This requires more work rather than just changing the text styles from a central location.
To be aligned with CSS when in dev mode on Figma, CSS would be different.
Here's an article from Figma on text styles best practices.
Potentially blocked by https://github.com/grommet/hpe-design-system/issues/3392
If we do this work now, we might end up doubling back on work if we switch fonts over.
Create a Figma component for Heading and add to the library. Preference is to use a component instead of consuming Typography elements. This will allow any changes to font treatments to be made in one central location and any updates to be pushed to all instances through the component update process. With the current approach, this is not possible and requires a designer to update all instances individually. (additional background)
Considerations
Primary deliverable
Potential follow on deliverables