The documentation for the Telerik Design System says "Starting with themes version 9.0.0, the CSS Utilities are no longer included in the Telerik and Kendo UI themes package." 

This will be an issue for how I use the Telerik UI for Blazor package.  I use the CSS utilities extensively.  They should continue to be included in the themes.

If they are no longer in the themes, it will be very inconvenient to acquire them using NPM.  I have no other need for NPM in my Blazor project.  If I have to load them separately (which seems like a mistake to me) it would be much more "natural" if they would be distributed via NuGet.

Please consider a USWDS Theme.  I'm referring to the design system https://designsystem.digital.gov/

This support would be a great way to incorporate Telerik components into projects for US Goverment clients.

Material 3: 

Request for Telerik UI for Blazor toolkit and Figma UI Toolkit to support Material Design 3 (versus 2) guidelines published late October 2021. Competitors are supporting it.

Website is https://m3.material.io/

Hi, Team!

Currently, the Kendo Material theme is compliant with Material Design 2. I would like to request compliance with Material Design 3. 

I would like to request that Telerik host all of the required nuget packages for Telerik.ui.for.Blazor on Telerik's nuget server.

Currently, all of the packages are there except for Telerik.FontIcons and Telerik.SvgIcons which are hosted on nuget.org instead. This is inconvenient when using Package Source mapping, where ideally all Telerik.* packages can be sourced direct from Telerik.

Some of our customers prefer a seamless design integration of their individual software solutions into the SAP ecosystem (e.g. in context of the BTP platform). So it would be nice to have a SAP Fiori theme like in Kendo UI for jQuery:

• https://docs.telerik.com/kendo-ui/styles-and-layout/less-themes/overview

We would like to use Kendo React to build a micro frontend UI but we did not found any relevant information that this is currently supported.

The main issue we are facing is how it isolate Kendo theme styling between different micro frontends.

Let's say we have 2 micro frontends A and B:

- A is using Kendo v6.

- B is using Kendo v7 (or some other future/past version).

Both of them will include their global Kendo styles which will collide.

After some investigation, we came up with 2 possible approaches:

1. Isolating micro frontends using shadow DOM. This is the most common technique but unfortunately not supported by Kendo React yet.
2. Prepend custom class to all Kendo CSS selectors (for example ".microfronend-a .k-button" instead of just ".k-button").

We have experimented with the second approach and it seems like a way to go. It also required to append all popups to root DOM node of a micro frontend which can be done easily using PopupPropsContext.

But adding a class to all Kendo CSS selector is technically not a trivial task. It would be nice if Kendo supported this out of the box, for example by providing some SCSS configuration variable.

Are there plans to improve 2.0.0 compatibility with kendo themes? math/calc should still be backwards compatible.

When creating a custom build, it's highly impractical to trim down the theme css. The Less source breaks out common widget properties, but the primary themable file lumps all widgets together into a single massive file. It would be nice if this could be split apart further to trim out unused widget styles entirely.

It would be nice if Theme variables would be separated into a different file, to make it possible to import those variables into your own site.less. 
This way colors etc can be re-used across the entire site.

With the new changes,  many variables were removed (like $primary-button-hovered-bg).

It is now generated through internal sass functions - but unfortunately, it only supports mixing color with black/white. resulting in washed-out colors if you want a lighter hover color.

I would expect to have an option to have a more linear lighten/darken sass functions.

Looking at the Kendo theme - try-lighten / try-darken exist that take the same input parameters.

There is also $kendo-solid-button-shade-function - but it is not marked as !default and cannot be overwritten.

When you have a button inside a MultiSelect Footer template (for example), it is different visualized compared to the same button outside of the component. This comes from the k-list-container that is applied when a button is inside a toolbar.

-------ADMIN EDIT---------

A possible workaround for the scenario is to use custom styles as shown below:

<div class="row">
    <div class="col-2">
        <TelerikButton ButtonType="Telerik.Blazor.ButtonType.Button"
                       Icon="k-icon k-i-add"
                       Primary="true">
            New Value
        </TelerikButton>
    </div>

    <div class="col-10">
        <TelerikMultiSelect Data="@(
                                            new List<SelectListItem>()
                                            {
                                                { new SelectListItem { Text = "Text 1", Value = "Value1" } },
                                                { new SelectListItem { Text = "Text 2", Value = "Value2" } },
                                                { new SelectListItem { Text = "Text 3", Value = "Value3" } },
                                                { new SelectListItem { Text = "Text 4", Value = "Value4" } }
                                            })"
                            FilterOperator="StringFilterOperator.Contains"
                            Filterable="true"
                            TItem="SelectListItem"
                            TValue="string"
                            TextField="Text"
                            ValueField="Value">
            <FooterTemplate>
                <TelerikButton ButtonType="Telerik.Blazor.ButtonType.Button"
                               Class="my-nested-button"
                               Icon="k-icon k-i-add"
                               Primary="true">
                    New Value
                </TelerikButton>
            </FooterTemplate>
        </TelerikMultiSelect>
    </div>
</div>

@code{
    public class SelectListItem
    {
        public string Value { get; set; }
        public string Text { get; set; }
    }
}

<style>
    .k-list-container .k-button.my-nested-button {
        background-color: #ff6358;
        align-items: flex-start;
        align-self: flex-start;
    }

    .k-list-container .k-button-primary.my-nested-button,
    .k-list-container .k-button.k-primary.my-nested-button {
        /*copy the colors from the basic button*/
        border-color: #ff6358;
        color: #ffffff;
        background-color: #ff6358;
        background-image: linear-gradient(rgba(0, 0, 0, 0), rgba(0, 0, 0, 0.04));
        /*change the flex alignment form the parent container*/
        align-items: flex-start;
        align-self: flex-start;
    }
</style>

It would be awesome to have "style hooks" for all components - this can be implemented through css variables/properties and would allow for things like dynamic theming including support for dark mode etc.

Because css variables/properties can be read and written through javascript this would open up several new ways for dynamic layouts.

CSS variable/properties are supported on all current browsers except IE 11, and it is possible to implement them with a gracefull fallback.

Currently, using npm install --save @progress/kendo-theme-material will get the standard Material Design theme for use across the React Components, but why is Material Black not available this way? (npm install --save @progress/kendo-theme-materialBlack)