If you maintain an open-source project in the range of 10k-200k lines of code, I strongly encourage you to add an ARCHITECTURE document next to README and CONTRIBUTING. Before going into the details of why and how, I want to emphasize that this is not another “docs are good, write more docs” advice. I am pretty sloppy about documentation, and, eg, I often use just “simplify” as a commit message. Nonetheless, I feel strongly about the issue, even to the point of pestering you:-) 

 3. Can be used in proprietary works
The license policy allow you to use this piece of code even inside commercial (not open source)
projects. So you can use this software without giving away your own (precious?) source code.

Blazing into Summer 2.0: What’s New in Blazor in .NET 6?  

Pre-commit hooks with Husky.NET - build, format, and test your .NET application before a Git commit  

A quick guide on how to properly instantiate and use HttpClient in .NET

Front-End Web Development in Desktop Applications — a hands-on project with Blazor and .NET 6 

DWKit is a .NET BPM system made with simplicity and flexibility in mind. 

A developers guide to running WPF apps on Linux with .NET Core and Wine 

Rewrite a legacy application using DDD, TDD, .NET and CoreDdd library