I'm a full-stack software developer with over 15 years of professional experience. In my professional life, I was doing a lot of different things. From desktop applications to web apps and services, and also writing game engines and 3D modeling. I like to experiment with different technologies, and so it happened that I learned about Blazor from Microsoft. It was nice and easy to use, and I felt a need to create something for it. So I built a UI component library named Blazorise. Slowly it came to be one of the most used libraries for Blazor.

I worked for a couple of companies. The longest time I worked for a company(online travel agency) was nine years, where I was the main architect and developer of the in-house booking system. Lately, I started my own company, and now I'm self-employed.

I first created a UI component for my own project. But soon, I realized that it would be nice to release it as an open-source. At that time, Blazor was very young, and it was missing good UI libraries. So after some code cleaning, writing the documentation(which was new to me), I published it and announced it on some most common platforms.

The start was slow, but I never stopped working on Blazorise, and I think people started to use it because they felt it was good and will not be abandoned. And as a result, a lot more people coming in, I also felt more and more inspired. This brings us to today, where it is a quality product with a large and growing community.

Blazorise is a component library built on top of Blazor with support for CSS frameworks like Bootstrap, Bulma, AntDesign, and Material.

To abstract the UI library API from using any CSS framework and to easily switch between them, if needed.

Mainly time. When I first built the project, I had a lot more time since there were only my wife and me back then. But after we got our son, I try to play with him as much as I can. So working on Blazorise can be done mostly at night or on weekends(currently). Also, a big part that is challenging is communication with the community. Answering their questions and resolving problems takes time. But it is all part of the "job," so to speak. And I kind of got used to it.

Most of the things I planned initially are mostly done by now, so now the main plan is to polish the API, clean the code, add more comments, and release the final and stable 1.0 version.

By following the guide at the project repo https://github.com/stsrki/Blazorise, or reading the document on the main web https://blazorise.com/docs/start/.

Yes, here you go- https://blazorise.com/docs/

Basically, anyone who wished to fast prototype or build the single-page web application running on Blazor and .Net stack.

My company clients are all using the Blazorise. Some of them are private, so I cannot still show them, but for example, there is an ABP Framework where Blazorise is the main UI provider for their Blazor modules.

And soon, I hope to finish my own project for Blazorise that is going public(but it is still a secret).

It's hard to select; just look at the lost of changes done so far :) https://github.com/stsrki/Blazorise/issues/1472 But it will depend on users' needs and also on my time to work on it.

They can sponsor the project on Patreon, buymeacoffee and PayPal.