Customizing UI (Styling/Theming) while using Bit.BlazorUI components

[WALEED-NET]

Hi,

First of all, thanks for the great work on Bit Platform really impressive effort.

I have a question regarding Bit.BlazorUI and how it fits into real-world projects with custom designs.

In many client projects, we usually receive a custom UI/UX design that follows a specific brand identity. Because of that, we often end up:

• Rebuilding the UI using pure HTML/CSS
• Sometimes using tools like Tailwind
• Creating custom components from scratch to match the design exactly

Recently, we even stopped using some Blazor UI libraries (like MudBlazor and Radzen) because their default styles and component structures didn’t align well with custom design systems.

So my question is:

Is there a recommended way to leverage the functionality of Bit.BlazorUI components while fully customizing or overriding their styles to match a completely custom design system?

For example:

• Can we easily replace or override styles (CSS variables, classes, etc.)?
• Is Bit.BlazorUI designed to support design-system-driven development?
• Or is it better suited for projects that adopt its default UI style?

I’d really appreciate any guidance, best practices, or examples on how to approach this.

Thanks again.

[msynk]

Thanks for contacting us.

In bit BlazorUI, we developed a few ways to customize the final look and feel of components.

The first and most important one is using the built-in Theme features described in the Theming page of our docs (https://blazorui.bitplatform.dev/theming). For example, you can easily override CSS variables for most common use cases.

The second approach is the Classes/Styles parameters of each component that enable developers to customize every part of the components by assigning specific CSS attributes to them.

Another way is to directly override the CSS classes (the ones that start with bit- identifier) assigned to the part you need. This approach is not suggested since the CSS class names of our components are not part of our official public api and they are subject to change in the future, but it can be a workaround in some cases.