| hidden | true |
|---|
As soon as your Token project includes Themes, there are JSON files created by the plugin to save your configuration data so it can be shared with developers. Once developers have the new Themes files in your external storage provider, they can use that data in their transformation process to turn the themes file into usable code.
{% include "../.gitbook/includes/transform-tokens-default-message.md" %}
SD-Transforms generic package includes a specific transforms to convert Tokens Studio themes into individual theme files for all possible permutations
→ SD-Transforms Read-Me Doc, Theming
If this is the first time you are working with Themes in your project, theres a couple things you'll want to do in the Plugin Settings make the transformation process as simple as possible:
| Sync to a remote storage provider, like GitHub, GitLab, Bitbucket or Azure DevOps. | cardHeader-sync-remote-overview.png | remote |
| Configure your sync settings to save to a folder in your repository with multiple files. | cardHeader-sync-remote-multi-file.png | remote-multi-file-sync.md |
Mentioned in this Guide
- SD-Transforms Read-Me - Theming
Community resources:
- None yet!
{% include "../.gitbook/includes/something-to-share-subm....md" %}
Tokens Studio Plugin GitHub - Open issues for Themes
{% include "../.gitbook/includes/bug-report.md" %}
- None
{% include "../.gitbook/includes/featurebase.md" %}