How can we ease adoption for designers/developers that have existing components in use today?
Proposed Solution
This is a feature that @Chessel and @lwnoble were discussing in our Landing Page call today. It would allow someone to bring their component to our project and generate design tokens from it that can be ultimately consumed and used in Theme Builder. An example would be that I have a button in my component library that already has styling information like foreground and background colors, typography, etc. I direct a tool to it (e.g. load it into Figma via plugin?) and the tool would generate the design tokens from the styling in the component that then could be eventually imported into a Theme Builder design system.
This would be used to support the BYOC (Bring Your Own Code) effort that we are trying to define.
Suggestion/Concern
How can we ease adoption for designers/developers that have existing components in use today?
Proposed Solution
This is a feature that @Chessel and @lwnoble were discussing in our Landing Page call today. It would allow someone to bring their component to our project and generate design tokens from it that can be ultimately consumed and used in Theme Builder. An example would be that I have a button in my component library that already has styling information like foreground and background colors, typography, etc. I direct a tool to it (e.g. load it into Figma via plugin?) and the tool would generate the design tokens from the styling in the component that then could be eventually imported into a Theme Builder design system.
This would be used to support the BYOC (Bring Your Own Code) effort that we are trying to define.