When the ThemeBuilder project has custom variables or variables exported from Figma in the output _tokens.scss file all variables are with the ‘tb’ or ‘figma’ prefix.

It will be good if these prefixes can be configuration options for the project and users can choose what prefix (or no prefix) should use. 

Consider the option to expose predefined classes of HTML elements from the Kendo themes. This would allow atomic customization and mapping to other imported variables (like ones imported from Figma designs).

For example:

An option to style the H1 header from the Kendo theme, which has the .k-h1 class. 

Add a new smart code editor as a variant of the Property Grid with all visual properties. Do not replace the property grid with this editor. They can live next to each other in different tabs. The smart code editor should support all features of the property grid but with advanced functionalities.  

1. Show all kendo styles attached to the selected layer in a text format 
2. Marks which style is overridden by user styles
3. Users can add any CSS property, not just the one listed by the Proprty grid editors. 
4. Intellisense for CSS properties, something like:

5. Intellisense for using sass/css variables – the editor can recognize the property name and list only corresponding tokens for example – background – shows color tokens, box-shadow – shows effect tokens.  Something like:

Consider providing export options for fonts - for example the one requested below:

...

I would like to request the inclusion of a non-exportable option in the Font Manager. Specifically, I suggest adding an additional field that allows users to choose whether to include a particular font in the "_fonts.scss" file or not.

The purpose behind this request is to utilize these fonts within the ThemeBuilder Pro to observe the visual outcomes (including Typeface & Icon fonts). However, it I do not want to generate these fonts in the final zip since I already have fonts with the same names in my application. I solely require the font names to be present in the "_tokens.scss" file.

Themebuilder used to export non compiled css

Now it's only compiled, and it's not easily plug and play with my current npm bundler.

Please bring back option to export non-compiled css

Consider providing a configuration file that stores information about mapped variables (e.g. like Figma variables mapped to Kendo variables)

Example scenario:

1. Create a new Figma design based on UI Kit
2. Export it to ThemeBuilder
3. Map the 3rd party or figma-styles to the ThemeBuilder styles.
4. Save the mappings between them as some external config file 
5. When I create a new project based on my customized UI kit and I export it to ThemeBuilder
6. Instead of re-doing for a new project the mappings for a couple of hours again by hand, load up the mappings file which I saved from the previous project and the tools just connects the dots.

I am getting this error, but am not able to revert the changes nor does it say where exact the error is. Do I have to start all over again!?
In my opinion the whole ThemeBuilder is still in Beta.

I suggest to implement a protocol tool with which you can revert the last 10 changes made in to the theme!

Hi,

I would like to build a Sass theme using the Telerik Sass theme builder. My theme should look like the classic-silver.css theme (like provided at href="https://kendo.cdn.telerik.com/themes/6.2.0/classic/classic-silver.css) with a few minor changes.

• Is it possible to load the classic-silver.css theme into the Telerik Sass theme builder in order to then modify it?

If yes, please give me instructions how to do that.

Regards, Manu

As the subject suggests, I think the ability to support multiple swatches in a single project would be a fantastic addition to Themebuilder!

This change would allow a user to select a theme that'll encompass an app's light mode, and once finished, select a separate theme to repeat the process for dark.

As it currently stands, separate Themebuilder projects need to be created in order to separate light and dark themes. 

Thank you in advance for your consideration!

Add the ability to style combined state: e.g. selected:hover:active.

Currently, you can style these states separately.

We started using Kendo / ThemeBuilder in our existing project which is using this root font size:

html {
    font-size: 10px;
}

This obviously cause issues with Kendo themese and ThemeBuilder which expects this value to be 16px.

Is there a way to configure this in ThemeBuilder or could this be implemented in the future?

Alternative solution would be to switch to 16px in our project. Which means we would have to recompute all CSS values which are using rem units.

I want to upload 2 variants of the same font (let's say Roboto with weight 300 and 500).

Then I want to configure the same font family for both of them.

This is currently not allowed (see attached screenshot).

I have to choose different names which results in an export like this:

@font-face {
  font-family: Roboto300;
  src: url('../fonts/roboto-v18-latin_latin-ext-300.woff') format('woff');
  font-style: normal;
  font-weight: 300;
  font-display: auto;
}

@font-face {
  font-family: Roboto500;
  src: url('../fonts/roboto-v18-latin_latin-ext-500.woff') format('woff');
  font-style: normal;
  font-weight: 500;
  font-display: auto;
}

But what I want to achieve is this:

@font-face {
  font-family: Roboto;
  src: url('../fonts/roboto-v18-latin_latin-ext-300.woff') format('woff');
  font-style: normal;
  font-weight: 300;
  font-display: auto;
}

@font-face {
  font-family: Roboto;
  src: url('../fonts/roboto-v18-latin_latin-ext-500.woff') format('woff');
  font-style: normal;
  font-weight: 500;
  font-display: auto;
}

My use case is that I want to set the font family only once and the just set different font-weight for individual components.

Also, we have migrated to Kendo / ThemeBuilder in our existing project which relies on fonts to be configured this way.

The style for dialog actions is exported with the following selector 

.k-dialog-wrapper .k-window.k-dialog .k-window-actions.k-dialog-actions.k-actions.k-actions-stretched

This is not applied when I switch actions bar to a different layout than the default

<DialogActionsBar layout="start">
</DialogActionsBar>

.k-actions-stretched