Situation
Our DS token system currently supports 3 viewports: Desktop, Tablet, Mobile.
Additionally, the DS has different grids defined per viewport:
➡️ As you can see, Tablet MD and Tablet SM have different margins.
Up until now, the majority of tokenized components were not affected by this, meaning: The tablet components were not intended to change between these 2 viewports.
Challenge
With the upcoming tokenization of [base] Header and [base] Footer, there will be design differences between the "Tablet MD" and "Tablet SM" grids.
➡️ How to approach this issue? ⬅️
Brainstorm possible solutions
- Option 1) Eliminate "Tablet MD" or "Tablet SM" grids
- Option 2) Hardcode any differences (possible?)
- Option 3) .... ?
Components which possibly face the same issue
Situation
Our DS token system currently supports 3 viewports: Desktop, Tablet, Mobile.
Additionally, the DS has different grids defined per viewport:
➡️ As you can see, Tablet MD and Tablet SM have different margins.
Up until now, the majority of tokenized components were not affected by this, meaning: The tablet components were not intended to change between these 2 viewports.
Challenge
With the upcoming tokenization of [base] Header and [base] Footer, there will be design differences between the "Tablet MD" and "Tablet SM" grids.
➡️ How to approach this issue? ⬅️
Brainstorm possible solutions
Components which possibly face the same issue