[TIP] Visit our website at https://material-blazor.com for a full Material.Blazor demonstration.
Material.Blazor is a lightweight Material Theme web development platform (version 9.0.0) component library for ASP.NET Blazor that is rigorously faithful to the Material Theme's design philosophy, markup and code usage. This docs site along with our demonstration website gives you a deep dive into Material.Blazor.
Material Theme has very specific and detailed guidance showing web designers how to build web apps with HTML, CSS and JavaScript. Since neither Blazor for WebAssembly are directly supported, Blazor developers either need to roll their own components or use a component library such as Material.Blazor. This is available at https://www.nuget.org/packages/Material.Blazor.
Material.Blazor isn't the only Blazor component library for Material Theme and we encourage developers to look at others including open source projects such as MatBlazor, Blazorize and Skclusive.Material.Component, or commercial products such as those from Telerik, and Syncfusion; this is not an exhaustive list and there may be others. So why did we create Material.Blazor as yet another option? Because we had some overriding objectives and to our taste this required a new library focussing on the following:
- Lightweight components that require the minimal possible setup or boilerplate Blazor coding and without intensive startup processing;
- An entirely native Blazor experience for Material.Blazor's consumer, using JavaScript Interop within Material.Blazor only where absolutely necessary, such as when initializing individual components to apply things like ripple and drop down menu functionality from the Material JavaScript libraries in the same manner as required for any other Material Theme web application;
- A balanced approach (or at least what we think is balanced) to component customization: enough to be functional but keeping things to the point and maintainable;
- A native Material Theme HTML/CSS experience where a developer wants and expects to use Material Theme's HTML Markup and CSS:
- Material.Blazor keeps out of a developer's way when she wants to follow Material Theme's guidance rigorously and take full advantage of its theming capability.
- We don't help you with styling/CSS. Whether you are theming or just tailoring the styles of individual components within a
<div>block, you need to be very familar with Material Components Web. If you think you like or dislike the look of one of our "core" Material.Blazor components, what you're actually viewing is Material Theme as Google intend it, and which we aim to bring faithfully to you. - Similarly you need to manage your layout because Material.Blazor doesn't try to help out. This is so you can decide what layout system to use - Material Theme, Bootstrap or whatever you want.
- So: we just do components using Material Theme. Other libraries take a different approach, and if you have a different requirement you may want to consider other options;
- You'll find some different themes on our website just to give you a flavour of what can be done. Note that these themes aren't really anything to do with Material.Blazor - we just decided to show that Material.Blazor works with themes built using material-components-web. Click the button on the top right of the top app bar. See the code base (same repo as this) to see how we did it.
- We've built some added value "plus" components derived from core material theme components but that are not strictly material theme themselves. These include an autocomplete box, a confimration dialog and formatted numeric input fields. We also provide a date picker and paginator, each of which follow Material Theme specification in the absence of a Material Theme css/js implementation;
- We aim for Material.Blazor to employ best practice for Blazor development. As a starting point this should be considered as being defined per this video from NDC London, January 2020; and
- Permissive MIT license and a clear contributor code of conduct.
Material.Blazor is forked from Steve Sanderson's experimental RazorComponents.MaterialDesign experiment. That project struck the balance we sought of giving easy to use, performant Blazor components in a lightweight, native Material Theme setting.
We also want to acknowledge the work of
- Vladimir Samoilenko (@SamProf on Github) for his work on MatBlazor. MatBlazor code was referenced and some small parts of the code were copied to be part of Material.Blazor (ClassMapper and StyleMapper).
- Chris Sainty (@chrissainty on Github) for his work on Blazored/Toast which is the basis for MBToast.
- ℳisterℳagoo (@mistermag00 on Twitter) for the
@:@{construct used in MBPagedDataList and Peter Morris (@mrpmorris on Github) for demonstrating this with code that we forked in Blazor University, christening it the "wig pig" - head to Blazor University to see why.
See the Components/Services/Utilities documentation
