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
There is often questions about the CTI structure and which categories and types are available to use in the built-in transforms and formats. Let's update our documentation to better reflect the categories and types used by built-in transforms and formats.
For those wondering right now, here is a start:
color (none of the types below the color category are used to apply different transforms, a color is a color. These types are just generally used)
background
font
border
size
font
icon (icon and font types in the size category are important for distinguishing between using DP and SP units in Android)
padding
border
asset (used for images and font files)
content (used for strings)
icon (this is assuming you are using an icon font with specific unicode characters)
The text was updated successfully, but these errors were encountered:
Fixes#571#159#605
* Renamed "style properties" to "design tokens"
* Adding tokens and allTokens to the core internal data structure to be consistent with this change. This is purely additional, properties and allProperties still exist and this should not break existing code. Moving forward examples should use tokens rather than properties.
* properties.md -> tokens.md
* Adding more content in this doc page about:
* All potential attributes #605
* Default attributes Style Dictionary adds
* More info on what categories the CTI currently supports #571
* Information on file formats for token files, including JS modules #159, and custom parsers for token files
* Updated broken links (linking to "master" branch instead of "main")
* Updated the examples page with all new examples
* Added a page on custom parsers
* Added information about transitive transforms
* Removed "docs/build_process.md" in favor of "docs/architecture.md" because the content was mostly the same.
* Cleaned up configuration content
* Updated language around config file formats and how to define the configuration
* Added information about configuration attributes and separated it out into sections: top-level config attributes including customization, platform attributes, and file attributes, for readability
* Cleaning up some spacing and headers in markdown files
There is often questions about the CTI structure and which categories and types are available to use in the built-in transforms and formats. Let's update our documentation to better reflect the categories and types used by built-in transforms and formats.
For those wondering right now, here is a start:
The text was updated successfully, but these errors were encountered: