You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The aim of this issue is to study and implement the elevation tokens taking into account the cohesive multi-platform approach, the customization by libraries inheriting OUDS Web, but also what we're using for OUDS Web: Boosted, Bootstrap 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 Web.
These tokens cannot be used by developers using OUDS Web.
Semantic applications: Depends on raw primitive values.
Mapping between these tokens and the raw primitive values will be customizable by libraries inheriting OUDS Web.
These tokens can be used by developers using OUDS Web.
Component applications: Depends on semantic applications.:
Mapping between these tokens and the semantic tokens should rarely be customized by libraries inheriting OUDS Web.
These tokens can be used by developers using OUDS Web.
Description
The aim of this issue is to study and implement the elevation tokens taking into account the cohesive multi-platform approach, the customization by libraries inheriting OUDS Web, but also what we're using for OUDS Web: Boosted, Bootstrap etc.
Reminder: there will be in the end 3 layers of tokens:
Tokens: Elevation
Raw primitive values
X
Y
Blur
Spread
Box shadow (Composite)
Caution
Figma doesn't accept composite tokens
Semantic applications
X
Y
Blur
Spread
Color
Box shadow (Composite)
Caution
Figma doesn't accept composite tokens
Study
Technical details
TODO
The text was updated successfully, but these errors were encountered: