When an element is selected in ThemeBuilder, it shows its Parts and Properties on the right and a Live Preview at the bottom. I would really benefit from seeing the HTML code/markup (snippet), e.g. `<button kendoButton themeColor="primary" fillMode="flat">Button</button>`. I'm trying to decipher what attributes I should be using by looking at the applied classes, but it's not always 1-to-1 or clear.
I need to be able to enter `rem` (or even `em`) values for metrics like `padding`.
Currently, in ThemeBuilder there is a template that allows you to style the icon of a header cell that is filterable.
However, we need to be able to style the icon in a header cell that triggers the ColumnMenu (the more icon)
https://demos.telerik.com/aspnet-core/grid/column-menu
https://www.telerik.com/kendo-react-ui/components/grid/interactivity/column-menu/
requested through t.1655985
It would be helpful to add a feature to ThemeBuilder that allows users to create theme variable modes based on typography variables, similar to the existing feature that lets them create themes based on color and metrics.
This will enable users to generate different themes within a single project by simply changing the fonts used.
Requested through t.1656320
Currently, in ThemeBuilder, the generated styles for the Telerik/Kendo component Breadcrumb are only for the collapse mode "wrap". However, in Telerik UI for Blazor, Kendo UI for Angular, and others, the Breadcrumb component supports different collapse mode values, such as "auto" and "none":
https://docs.telerik.com/blazor-ui/components/breadcrumb/collapse-modes
https://www.telerik.com/kendo-angular-ui/components/navigation/breadcrumb/collapse-modes/
Consider providing templates to allow the generation of styles for other collapse modes.
Requested through t.1660021
Consider generating utility classes for variables to apply and reuse styles easily. For example, the user defines a color variable in ThemeBuilder called "component," and this makes ThemeBuilder generate utility classes:
.k-color-component {
color: #ffeb3b;
}
.\!k-color-component {
color: #ffeb3b !important;
}
.k-bg-component {
background-color: #ffeb3b;
}
.\!k-bg-component {
background-color: #ffeb3b !important;
}
These utility classes can then be applied and reused in code outside of ThemeBuilder:
<div class="k-color-component"></div>
Currently you can only use and customize the default 6 Chart series colors (Kendo Colors Series A, B,C,D,E and F) using ThemeBuilder. Any additional ones needs to be defined in the component code. This is not ideal if you want to manage all colors from ThemeBuilder.
The request to have either have the ability to add new Chart series colors in the ThemeBuilder which you can use with the chart or have more variables exposed at the beginning 25+
Currently, ThemeBuilder exposes templates for the states of the TabStrip items. However, the changes apply to all positions of the TabStrip. This is inconvenient if you want to apply changes only to one of its positions. Also, these items' states have specific styles coming with the keyword "!important", which the default templates do not override.
Consider exposing templates for these states based on the position of the TabStrip component.
Requested through t.1666111.
tb-custom-primary: #014d5b !default; //Is the value if not defined in final scss
tb-primary: tb-custom-primary;
-----------------------------------------------
index.scss
$tb-custom-color: #34b232; //Now I can define the final value for variable
@import '_tokens'
it would be useful to add it in ThemeBuilder UI.

In Sass is possible to define à variable like this
$primary: red;
$primary-filter: rgba($primary, .5);
But this possibility is not supprted by ThemeBuilder
It may be usefull for variation of same color in theme whit only one variable to adjust.
Sometimes, errors occur in ThemeBuilder due to various reasons.
Consider including indicators in these errors to let the users know where they are located so they can possibly fix them through ThemeBuilder's user interface if applicable.
Requested through t.1667194.
Sometimes, when using the Export Font Icons functionality of the ThemeBuilder Plugin for Figma, the export freezes with "Sending data to server: 0%":
This is due to how Figma handles the export of icons.
Consider implementing a mechanism for indicating the problematic icons so that users can remove/update them and make them eligible for export.
Currently, there are no templates for modifying the sort icons of the filter cells of the TreeList component. There is a template for the Filter Row, which refers to the Grid component. However, the part with the sort icon is not connected to the Grid, as modifying it there doesn't reflect the change in the TreeList.
Consider exposing a templates for these icons.
When exporting only selected components, it would be incredibly beneficial if ThemeBuilder could automatically generate separate override files specifically for those components. This approach would keep the codebase more modular, improve performance, and better serve applications relying only on certain Kendo components.
Requested through 1674517
Consider adding a functionality that will allow the bulk export of component variants in Figma while using the Figma plugin for ThemeBuilder.
For example, an option to export and create all variants of the Button in the Telerik UI kit
Consider and research the options for automatically exporting and mapping styles from the Telerik UI Kits to the built-in Telerik/Kendo templates in ThemeBuilder.
Currently, when using Telerik UI Kit alongside the Figma plugin for ThemeBuilde, one can do one of the following:
- Export only the styles *& variables and then manually map the styles in ThemeBuilder
- Export and create custom components, which won't be connected to the Telerik/Kendo components and will have a custom HTML rendering.
Consider exposing a styling template for the PropertyGrid component
https://demos.telerik.com/kendo-ui/propertygrid/index
Expose styling templates for the Wizard components available in the Kendo/Telerik suites
https://github.com/telerik/kendo-themes/tree/develop/tests/wizard
https://demos.telerik.com/blazor-ui/wizard/overview
https://www.telerik.com/kendo-react-ui/components/form/wizard