Hello Kurt,

Our themes apply styles to specific CSS classes, which are used by our components. The themes don't define styles for generic HTML elements that are not related to our components. There are very few exceptions, which are related to typography.

Thus, the desired project template will require one or more of the following:

• We should expand our themes to style generic HTML content and increase the web asset footprint for everyone.
• We should create multiple versions of site.css that style the Telerik Blazor project template.
• We may even need to design our own project template from scratch.

I guess we can agree that the default Blazor project template of Visual Studio doesn't fit everyone' needs. We can be sure that the same will apply for our own project template, no matter what we put inside it.

The important bit in the whole app theme management process is the CSS file switching and we have this documented due to popular demand, although it's not part of our API. From this point on, each app should provide its own stylesheets, which are tailored to the specific content and business requirements.

Our belief is that a project template, which provides multiple themes for the generic content is outside the scope of our product and will provide only marginal value.

Let me know if you have any thoughts.

Regards,
Dimo
Progress Telerik