[Replace this first paragraph with a short description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters. Until you edit this text or create topics, this category won’t appear on the categories page.]
Use the following paragraphs for a longer description, as well as to establish any category guidelines or rules.
Some things to consider in any discussion replies below:
What is this category for? Why should people select this category for their topic?
How is this different than the other categories we already have?
Do we need this category?
Should we merge this with another category, or split it into more categories?
Blazor is a Web UI framework based on C#, Razor, and HTML that runs in the browser via WebAssembly, per Wikipedia Blazor
This category should focus on specifics of the Blazor framework and Razor components. This tag should be appropriate for posts that refer to either Client-Side or Server-Side Blazor.
This tag is closely related to the WASM tag. A good blog post explaining where Blazor sits in the browser-based client UI stack (and it’s relationship to WASM) is Scot Hanselman’s blog What is Blazor and What is Razor Components? dated March 2019.
The Blazor framework is on the roadmap for a supported feature in .Net Core 3.0 release. The number of posts appropriate for this tag may begin to increase after .Net Core 3.0 is officially released and supported
Current (as of May 2019) Microsoft home page for Blazor is Blazor(Client)
[Author’s Note] - mythz, is this the appropriate way to update the category’s description? Do you copy this reply into the category description and delete this reply? or should I do something different?