In order to deliver theming, we need to support a fork of the Auro design tokens to create JetStream Design Tokens.
Possible Solution
There are two ways we can do this. One, host all the tokens in a single repo and configure a way to distribute two sets of tokens. Two, we simply clone the repo and rename.
Specification
When comparing tokens between Auro and JetStream, there is a fair number of tokens that are consistent between the two. If the direction includes cloning the repo, we should consider not duplicating the shared tokens.
E.g. we might want to consider that users install both Auto and Jetstream and when there is a common token, that will use Auro and the Jetstream token would override the Auro token.
General Support Request
In order to deliver theming, we need to support a fork of the Auro design tokens to create JetStream Design Tokens.
Possible Solution
There are two ways we can do this. One, host all the tokens in a single repo and configure a way to distribute two sets of tokens. Two, we simply clone the repo and rename.
Specification
When comparing tokens between Auro and JetStream, there is a fair number of tokens that are consistent between the two. If the direction includes cloning the repo, we should consider not duplicating the shared tokens.
E.g. we might want to consider that users install both Auto and Jetstream and when there is a common token, that will use Auro and the Jetstream token would override the Auro token.
A worksheet of data from @leeejune - worksheet
Recomendation
@leeejune pair with @jordanjones243 to ensure quality of code reference. There is a lot of data in the spreadsheet.
Exit criteria
This issue will be considered closed once there is a set of tokens that any engineer can subscribe to that is specifically for JetStream UI.