Tokens Studio has several independent Token Types that are not officially recognized in the W3C DTCG Specifications:
Spacing
Sizing
Border Width
Border Radius
The spec defines a Dimension Token as the preferred type for these properties.
If we want to fully align with the spec, Tokens Studio is required to phase out these ‘unofficial’ Token Types. However, we believe the choice should be yours!
We have a custom transformation that changes these Token Types to dimension
included in the SD-Transforms npm package and we’ve introduced a dimension
as its own Token Type.
How does having these properties as independent Token Types influence your workflow?
What would the impact be if these Token Types would be deprecated, assuming migration was taken care of by Tokens Studio?
Please authenticate to join the conversation.
💬 Discussion
💡 Plugin Feedback
🔶 DTCG - W3C Specification Align
3 months ago
Sam - Tokens Studio
Get notified by email when there are changes.
💬 Discussion
💡 Plugin Feedback
🔶 DTCG - W3C Specification Align
3 months ago
Sam - Tokens Studio
Get notified by email when there are changes.