The community members discuss the need for a way to transfer design tokens between projects or define them at an account level, to improve design and development velocity. The post suggests that implementing JSON import-export functionality for design tokens could be a sensible approach.
The comments suggest that copying the content of a "style guide" page into another project can transfer the tokens, but this only transfers the tokens that have been applied to existing controls, not any additional tokens that may be needed. The community members also note that copying individual controls from one project to another may be a more straightforward way to transfer the associated tokens.
It would be really helpful to be able to either transfer design tokens from one project to another or, alternatively, define tokens at an account level, so that people are able to re-use them across all of their projects. One of the major issues is that if you have a lot of tokens to manually add for each project, you lose a lot of velocity in design and development.
I would see design tokens being exportable and importable, being one of the more sensible approaches since that could potentially be done by implementing JSON import-export functionality. Where the JSON would contain the design token collection and their values.
We usually recommend to put all tokens into "style guide" page, you can copy its content and paste into another project. All tokens will be copied as well.
Yep. I figured that bit to be the best way of workin, but the problem is that the page is not transferrable between projects. Or if it is, I don't know how to do it. And it also means that you are only transferring tokens you've applied to existing controls, not the ones you might need for something further down the road
Like tokens in isolation maybe not make sense. Some controls carry a few tokens and selecting it from some list is not easy task. Copying whole control is much more straightforward.
