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. 

Add a Last Cell template for the Grid component similar to the First Cell template that we currently have exposed.

Requested through t.1626999

The Kendo Themes recently introduced an accessibility swatch A11y for the Default Ocen Blue theme https://www.telerik.com/kendo-angular-ui/components/accessibility/accessibility-swatch/

Feature request: Support for the Ocean Blue A11y Accessibility Swatch in ThemeBuilder.

Greetings,

I know it is possible to access these variables in SCSS given the right setup. However users might not always be in position to have that, for various reasons, e.g.:

• a person that doesn't have the time to setup that
• a person that doesn't want to setup that
• a person that doesn't know how to setup that
• a person that isn't authorized to setup that and has access only to the final CSS file

I think it would be nice to make ThemeBuilder available as CSS custom properties (aka "CSS variables"). Some info about this idea (I guess ThemeBuilder uses SASS behind the scenes?): Convert Sass variables to CSS variables · Issue #3091 · sass/sass (github.com)

Regarding the possibly large amount of variables, I think the ones visible in ThemeBuilder would cover the vast majority of cases.

Whether you intend on doing this or not, could you please document how the exported CSS file is generated behind the scenes? I tried reverse-engineering it since I originally wanted to be able to work on SASS code and then obtain the same result as ThemeBuilder. My guess:

1. SASS generates a minified CSS file (with a sourcemap)
2. minified CSS then go through Autoprefixer (PostCSS plugin)
3. minified and autoprefixed CSS then go through calc (PostCSS plugin)

Thanks!

I have a grid with a column that contains clickable text in <a> tags and want it to be obvious to the user that this is clickable, by having the text display in blue.

However, there is a CSS class being applied that is preventing the styling from showing:

.k-grid a {
    color: inherit;
    text-decoration: none;
}

Is it possible for me to modify the styling of these links within ThemeBuilder and not have to add a custom global style override? I have not found any way of changing this.

Thanks

Consider exposing a ThemeBuilder template for the Popup component.

https://www.telerik.com/kendo-react-ui/components/popup/ 

https://docs.telerik.com/kendo-ui/controls/popup/overview 

https://docs.telerik.com/blazor-ui/components/popup/overview 

https://www.telerik.com/kendo-angular-ui/components/popup/ 

https://github.com/telerik/kendo-themes/blob/develop/tests/popup/popup-no-data.html 

Currently, there is no way to style the different states (e.g. hover) of the Grid's Column Menu items through ThemeBuilder.

Consider exposing templates for those states. 

Requested through t.1661051.

Currently, the Drawer components (such as Drawer and Drawer Mini) come with a right border that can't be modified through ThemeBuilder:

Consider exposing a template that allows to modify this border.

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, the external CSS files come before the overrides generated through ThemeBuilder. Therefore, it becomes problematic to override these ThemeBuilder overrides with external styles.

Consider allowing the user to choose the order in which the external styles are applied —whether they should come before or after the ThemeBuilder overrides.

Requested through t.1662556.

Currently, there is no exposed template for the nested span of the Notification component. It becomes problematic if you have applied some styles (e.g., the color of the text) to the HTML element "span" and you want to override them through ThemeBuilder.

Consider exposing such component part.

Currently, the Checkbox component doesn't have an exposed template for modifying the pseudo-element ::before. If they decide to use font icons to style the icons for the checked and indeterminate states, they cannot achieve this through ThemeBuilder.

Requested through t.1663139.

Currently, the Calendar that is used in ThemeBuilder is considered "infinite", where we can change the months by scrolling. However, in Telerik UI for Blazor, the only calendar available is the "modern" one, which uses arrow buttons to change months. As a result, some of the styles we apply to the calendar templates in ThemeBuilder don't work with this calendar. Additionally, we are unable to style certain elements, like the arrow buttons, using ThemeBuilder.

Consider exposing templates for a "modern" Calendar component.

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.

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

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

I am using the Sass ThemeBuilder to regenerate stylesheets with the themes that we use on our site in order to get the latest version of the styles. One of those styles includes the color Blue Gray. I am able to select and download all other styles and colors except for when I select Blue Gray. When I select the color and click download I receive the a `500 - Internal Server Error`.

Hello,

Could you please add editable states to the PanelBar > Child Item Level 2, so that it can have a proper indent?

Thanks

Hello,

Would you please add a focused state to the tabs component in the ThemeBuilder.

Thanks