MudBlazor VS DocFX

I don't think that new Identity pages will work with MudBlazor out of the box. Take a look at this GitHub issue: https://github.com/MudBlazor/MudBlazor/issues/7805

The Blazor Server application uses the open source component MudBlazor, which I recommend to C# oriented developers. To keep the application simple, all data is stored in JSON files.

You could use Mudblazor and Codebeam Mud extensions.

Look up some Blazor UI / Component Libraries.Awesome-Blazor lists the more popular ones. The two I recommend are Mudblazor and Havit Blazor because the documentation is built using Blazor and the repos are open source on GitHub.

and you can use mudblazor components for free. https://mudblazor.com/

I'm creating a Blazor MAUI project using MudBlazor, and I'm looking for a way to refresh a page on Android using the pull to refresh feature. By now the best result I've found is to surround all the with a tag as shown here but this would mean refreshing the whole content on the page, NavMenu included. I've also tried to implement the BcdLib/PullComponent: with this one I can refresh only the body of the page but I can't achieve a smooth refresh animation like in the first method.

The load times and lighthouse score for the MUD Blazor site has put me off of Blazor entirely for anything public facing:

https://mudblazor.com/

This is a better looking version of what Java and C# have had for a long time (kudos to the author for that!), is that the inspiration for this tool?

https://docs.oracle.com/javase/8/docs/technotes/tools/window...

https://dotnet.github.io/docfx/

I saw the author mentioned in another comment that they found themselves peeping inside type declaration files "too often". While I do often use sites generated by the above tools to discover new API's that suit my needs, diving into the actual code using a good decompiler is still my first move, as it is often cheaper than seeking out the documentation online, and it will show me the actual implementation as well. So in my opinion there is no shame in looking inside the declaration files!

Tools like DocFx provide the ability to display the programmable functions in HTML pages. They are used with the following commands in the docfx folder:

AFAIK they use https://github.com/dotnet/docfx which can be too heavy for your case. We use mdBook for internal documentation (plain .md with mermaid plugin) and then serve it at docs.yourdevenv.com.

DocFX is a nice solution.

It uses DocFX

Some of the standard and well-maintained Tools for Comments are JSDoc for Javascript, DocFx for .NET, and JavaDoc for Java.

Actually, we use it for OptiTune, it's called "docfx" https://dotnet.github.io/docfx/

We would really prefer to use a somewhat generic pre-made tool for this (such as DocFX) compared to rolling our own solution. We can roll our own solution... But would prefer not to so that we can minimize development and maintenance overhead.