The aim of this issue is to study and implement the typography tokens taking into account the cohesive multi-platform approach, the customization by libraries inheriting OUDS Flutter, but also what we're using for OUDS Flutter: Flutter, Material 3, etc.
Define the possibilities
Define the constraints
Define the impacts
Implement the tokens (with a future Style Dictionary usage in mind)
Reminder: there will be in the end 3 layers of tokens:
Raw primitive values: Insertion of brand foundations.
These tokens will be customizable by libraries inheriting OUDS Flutter.
These tokens cannot be used by developers using OUDS Flutter.
Semantic applications: Depends on raw primitive values.
Mapping between these tokens and the raw primitive values will be customizable by libraries inheriting OUDS Flutter.
These tokens can be used by developers using OUDS Flutter.
Component applications: Depends on semantic applications.:
Mapping between these tokens and the semantic tokens should rarely be customized by libraries inheriting OUDS Flutter.
These tokens can be used by developers using OUDS Flutter.
⚠️ On hold until https://github.com/Orange-OpenSource/ouds-flutter/issues/25 is resolved
Description
The aim of this issue is to study and implement the typography tokens taking into account the cohesive multi-platform approach, the customization by libraries inheriting OUDS Flutter, but also what we're using for OUDS Flutter: Flutter, Material 3, etc.
Reminder: there will be in the end 3 layers of tokens:
Tokens: Typography
Raw primitive values
Font
Family
Weight
Size
Line-height
Letter spacing (%)
Letter spacing (px)
Paragraph spacing
Typography (Composite)
Semantic applications
Font
Family
Weight
Size
Line-height
Letter-spacing
Paragraph-spacing
Typography (Composite)
Display
Heading
Body
Label
Code
Study
Technical details
TODO