It is not specified in the file, but parsers that conform to this spec MUST be able to expose the path of a token. The names of the groups leading to a given token (including that token's name) are that token's path, which is a computed property. The $type property MUST be a plain JSON string, whose value is string, number, boolean, object, array, null or one of the values specified in respective type chapters. The $type property can be set on different levels: Tools MUST NOT attempt to guess the type of a token by inspecting the contents of its value. Otherwise, the token's type is whichever of the basic JSON types ( string, number, boolean, object, array or null) its value is.Otherwise, if any of the token's parent groups have a $type property, then the token's type is inherited from the closest parent group with a $type property.If the token's value is a reference, then its type is the type of the token being referenced.If the $type property is not set on a token, then the token's type MUST be determined as follows: Integrate them by defining a standard file format for expressing designĭesign tokens always have an unambiguous type, so that tools can reliably interpret their value.Ī token's type can be specified by the optional $type property. Tools and thus lower the work design system teams need to do to This specification aims to facilitate better interoperability between Migrate to different tools, they will need to update those integrations. Theīurden is therefore on design system teams to create and maintain their To export design tokens as a file, these are all tool-specific. While many tools now offer APIs to access design tokens or the ability Maintaining a "single source of truth" for design tokens andĪutomatically keeping design and development tools in sync with it Translation tools to then be converted into platform-specific code Together, so that design token data can flow between design andĮxtracting design tokens from design files and feeding them into It is often desirable for design system teams to integrate such tools Raw values in design specs and style guides. Documentation tools can display design token names rather than the.Into platform-specific source code that can directly be used by Translation tools exist that can convert source design token data.Shared values for design properties like colors and sizes. Design tools have begun allowing designers to label and reference. ![]() There is a growing ecosystem of tools for design system maintainers andĬonsumers that incorporate design token functionality, or would benefit Platform-agnostic way so that they can be shared across differentĭisciplines, tools, and technologies. This document was produced by the Design Tokens Community Group, andĬontributions to this draft are governed byĬommunity Contributor License Agreement (CLA), as specified by theĭesign tokens are a methodology for expressing design decisions in a This document has been published to facilitate Wide Review. Don't cite this document other than as work in progress. Its publication here does not implyĮndorsement of its contents by W3C or the Design Tokens Community Group This is a snapshot of the editors' draft. ![]() There is a limited opt-out and other conditions apply. W3C Community Contributor License Agreement (CLA) This document describes the technical specification for a file format toĮxchange design tokens between different tools.ĭesign Tokens Community Group. Draft Community Group Report 31 August 2022 Latest published version: Editors: Daniel Banks Donna Vitan James Nash Kevin Powell Louis Chenais Feedback: GitHub design-tokens/community-group
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |