Added Blazor

[spj2401Dev]

Hey, I think I added the first non JS Framework :O!

I added almost all the components except the 2 Webapp ones, because yea. I felt Blazor was too different and would require wayyy more files, so I thought I would just leave that out.

Also the Highlighter is not optimal. markdown-it (who knew) does not support razor syntax so I used the csharp syntax for now.

Have fun with Blazor :D

[driesdl]

What's the usecase for comparing a non-js-framework with every js-framework on the site?

[driesdl]

Resolve conflicts

[spj2401Dev]

I think it's really useful to have a non-JS framework as a cross-ecosystem reference point. It's really helpful to see the same UI tasks (state, props, events, lifecycle, etc.) side by side, as it helps separate "general component patterns" from "this is just how JS frameworks tend to do it." Its also great for teams that are choosing between stacks.
Blazor is a great choice here as its on the same page as the JS frameworks on Component Party when it comes to UI. So, building interactive, component-based UIs with parameters, local state, event handlers and lifecycle hooks, but using a different language/runtime.
What do you think about this for the project? Would it be something youd be interested in, or not so much?

[driesdl]

@spj2401Dev Thanks for your reply, great idea!