Change Details

Inspired by [[ https://docs.google.com/document/d/1bS34ARSi51zIORmMRp06VS9HYmi98SyHcqV8ecOQHrs/edit?ts=5f2bfa8b#bookmark=id.u44zf7iw0hja | recent conversations ]] and as seen in [[ https://designsystem.digital.gov/design-tokens/typesetting/overview/ | other design systems ]], it might be worth exploring the possibility of combining the current multiple typography tokens into reusable mixins to style component text. The aim of this task would be to abstract all styles, ideally in a single "typography" mixin, and allow implementers to use arguments to select and apply the style `@include typography(body)` in a simpler way. (That, or we could also create classes based on this mixin). The goals are: - Remove the need to specify styles for components' text repeatedly (e.g. when creating component tokens). - In case we can find an easy and non-costly way to export mixins: allow implementers applying styles to text in the application in a simpler way.

Currently, each time that the text style of a component (e.g. placeholder) or a typographic style of an application's interface (e.g h3) need to be specified, several individual typography tokens need to be defined again. There's no way to store and reuse the system's typographic styles in a way that would reduce time and ensure consistency. **ACs**: - The need to specify styles for components' text repeatedly is removed (e.g. as it was already done with the Label element) - System implementers can applying styles to text in the application in a simple way that ensures consistency. Note: Inspired by [[ https://docs.google.com/document/d/1bS34ARSi51zIORmMRp06VS9HYmi98SyHcqV8ecOQHrs/edit?ts=5f2bfa8b#bookmark=id.u44zf7iw0hja | recent conversations ]] and as seen in [[ https://designsystem.digital.gov/design-tokens/typesetting/overview/ | other design systems ]], it might be worth exploring the possibility of combining the current multiple typography tokens into reusable mixins to style component text.

Inspired by [[ https://docs.google.com/document/d/1bS34ARSi51zIORmMRp06VS9HYmi98SyHcqV8ecOQHrs/edit?ts=5f2bfa8b#bookmark=id.u44zf7iw0hja | recent conversations ]] and as seen in [[ https://designsystem.digital.gov/design-tokens/typesetting/overview/ | other design systems ]]Currently, it might be worth exploring the possibility of combining the current multiple typography tokens into reusable mixins to style component text. The aim of this task would be to abstract all styles,each time that the text style of a component (e.g. ideally in a single "typography" mixin, and allow implementers to use arguments to select and apply the style `@include typography(body)` in a simpler way.placeholder) or a typographic style of an application's interface (e.g h3) need to be specified, (That,several individual typography tokens need to be defined again. or we could also create classes based on this mixin). The goals are: - Remove tThere's no way to store and reuse the system's typographic styles in a way that would reduce time and ensure consistency. **ACs**: - The need to specify styles for components' text repeatedly is removed (e.g. when creating component tokens). - In case we can find an easy and non-costly way to export mixins: allow implementers applying styles to text in the application in a simpler way.as it was already done with the Label element) - System implementers can applying styles to text in the application in a simple way that ensures consistency. Note: Inspired by [[ https://docs.google.com/document/d/1bS34ARSi51zIORmMRp06VS9HYmi98SyHcqV8ecOQHrs/edit?ts=5f2bfa8b#bookmark=id.u44zf7iw0hja | recent conversations ]] and as seen in [[ https://designsystem.digital.gov/design-tokens/typesetting/overview/ | other design systems ]], it might be worth exploring the possibility of combining the current multiple typography tokens into reusable mixins to style component text.