Go straight to the site if you want: http://nudoq.org. You can then come back and continue reading :)
Compare some of the most popular NuGet packages API documentation sites:
You see the pattern? Huge navigation tree views, static content with no comments/community content, very hard (if not impossible) to search/filter, etc.
These are the product of automated tools that have been developed years ago, in a time where CHM help files were common and even expected from libraries. Nowadays, most of the top packages in NuGet.org don’t even provide an online documentation site at all: it’s such a hassle for such a crappy user experience in the end!
Good news is that it doesn’t have to be that way.