I don't understand the workflow now that the Unite UX tool was retired.
Our designers used your Figma UI kits for our custom Kendo React App and have built our design system.
How do I get it now to code with the logic of ThemeBuilder replacing Unite UX?
Thank you!
1 Answer, 1 is accepted
0
Radoslav
Telerik team
answered on 24 May 2023, 06:46 AM
Hello Sanja,
The problem with Unite UX was that the workflow for styling Kendo components was too complicated, and we fixed this with ThemeBuilder. The ThemeBuilder workflow is much easier and at the same time, it gets the best part of the Unite UX features – the developers inspect the styles in the Figma and apply the customization over the components in the ThemeBuilder.
Additionally for the next release after a couple of weeks, we will release a ThemeBuilder Figma plugin where the designers can export all design styles to the ThemeBuilder project and these styles will be converted to ready-to-use Sass or CSS variables.
"Additionally for the next release after a couple of weeks, we will release a ThemeBuilder Figma plugin where the designers can export all design styles to the ThemeBuilder project and these styles will be converted to ready-to-use Sass or CSS variables. "
Thank you, this was exactly what I needed.
Just a follow up question, will this plugin be a part of ThemeBuilder Pro or the basic free suite?
Thnx!
Radoslav
Telerik team
commented on 24 May 2023, 08:58 AM
Hi Sanja,
The Figma Plugin will be part of the paid version of ThemeBuilder.