Expose additional styling templates for a Grid component that uses stacked columns (a.k.a. as stacked display mode):

https://www.telerik.com/blazor-ui/documentation/components/grid/columns/stacked

https://demos.telerik.com/kendo-ui/grid/stacked-display-mode 

https://www.telerik.com/kendo-angular-ui/components/grid/styling-and-appearance/stacked-layout-mode 

Hello,

I'm building my first .net9+ Blazor Hybrid + Web app. I can see that theming is going to be a problem between the Blazor Web UI theme and the native app areas that use App.xaml resources. I'd like to request/suggest that theme builder can take a theme which is typically exported in CSS and also have the option to generate the App.xaml resources so my app native or using Web UI share a common theme.

Thank you.

This is an incredibly important feature for a tool like a "ThemeBuilder" to do.  There are too many colors for someone to easily swap out, which makes the tool hard to manage for color.  I know we can use another tool to create color palettes and then plug it in, but honestly this is one of the top things a ThemeBuilder should do. 

It should make swapping color categories simple by allowing you to select the colors for primary, danger, warning, tertiary, info, etc. and then the tool generates a color palette within the color family automatically. Then, if the user does not like any of the colors automated, they could manually swap them out like they do today.

Hi,

right now you are not able to style the adornments for example of a numeric textbox in ThemeBuilder.
It would be nice if that could be added.

Thanks,
Nina

Consider enhancing the ThemeBuilder applicaiton by providing options to export components  from ThemeBuilder to Figma with the idea that FIgma designers will have an easier way to create Figma files based on the Kendo/Telerik components and their  templates  (including variations, functionalities and states)

Requested through t.1684034

Consider adding support for CSS breakpoing / media queries in ThemeBuilder.

https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_media_queries/Using_media_queries 

https://www.w3schools.com/howto/howto_css_media_query_breakpoints.asp 

This will enable users to create response design directly within the ThemeBuilder application.

Requested through t.1682156

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 

Consider making the generated CSS to contain CSS variables instead of compiled CSS. Currently, that is possible only when using direct variables like $kendo-spacing-1.

However, with the current state (Q1 2025), ThemeBuilder will produce compiled value in the CSS when the variables are non-direct (refer to the first screenshot). In the example below the $kendo-spacing-7 is costom added to the $kendo-button-padding-x and as a result, will be compiled as a value

or when the variable is custom-created (second screenshot).

In the example, below the kendo-spacing-7 is used directly and is generated as variable, but $m y-variable is compiled as a value.

Requested through t.1679417

Consider exposing a styling template for the PropertyGrid component

https://demos.telerik.com/kendo-ui/propertygrid/index

It would be helpful for the "< Back" button on the Advanced Edit workspace to take you back to the same scroll position on the Live Preview page (history management).  Currently, the back button takes you to the top of the page.  This would be helpful when editing several components at the same time.

Consider adding support to set a data URL with SVG when creating a color variable

For example, that would allow the usage of different SVGs when switching between color modes and using components like the Switch

Current state:

The above means that it is not possible to use differently colored SVGs when using multiple color modes.

Requested through t.1679372

Hi,

I created a new Q4 2024 (SVG Icons) Kendo Default Theme.

When I try to apply any of the provided color swatches, I see a loading spinner for 30 seconds and a "Failed to save document" error.

When I checked the network requests, I noticed that PATCH https://themebuilderapp.telerik.com/api/v1/projects/67a267df70e5e715ec193d0e/variables method returns 500 Internal Server Error with "Transaction with { txnNumber: 11 } has been aborted." error.

Consider exposing a template or a component part for the DateTickerPcker > Time > Highlight part.

The styling option is similar to what ThemeBuilder currently has for the TimePicker template

requested through t.1676966

Hi Team,

I encountered an issue while exporting a few selected components from the theme build. When I use them in my application, I’m seeing variable-related errors in the index file.

Please refer to the screenshot below:

In the screenshot, you can see that I have not exported the AppBar, Badge, and BottomNavigation components. However, their variables still appear in the index file.

I’m currently using:

kendo-theme-material": "^10.1.0"

Kindly look into this issue.

Thanks

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 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

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

I modified a theme this morning and after changing a property got the error: "There are errors in SASS and it cannot be compiled to CSS.". Changing the property back to what it was before did not resolve the problem. Clicking the Undo button over and over and over did not resolve it. 

I started over with a backup taken yesterday and started reapplying changes. When I clicked "Export All" I once again got the same error. There is no way to recover from it. 

I've had ThemeBuilder licensed for some time, but this is the first week I've tried to use it in our application. It seems to be total garbage. I can't see any why forward with us using a tool that's going to randomly produce unrecoverable errors. 

We recently upgraded our theme builder to ultimate so we could migrate our theme builder project from R1 2023 to Q4 2024. After we did this there were some small changes we needed to fix but after that we followed all the normal installation procedures.

We are running angular 18 and have updated all kendo components to the latest versions.

After installing the new theme we also added/changed the way we imported the theme package following the documentation (using @use).

Most everything looks good but there is one large issue with several of our components and that is the kendo theme mixin  "k-color" is not working.

In several places there is no color or background color being set on the component(s). When i inspect the style i see     color: k-color(primary); is not working. dev tools states that the variable is wrong. i can only assume the mixin is not imported/being used.

Image of my description