..to help improving other documentations as well :)

This is a nice format but losing RSS Feed notifications is a drawback.

Add a link to reference source code to easily view source of current class/method

Support searching for parts of API names - e.g. index camel cased word parts.

Currently, there are no Results for "NullOrEmpty" - which is just a full part of "IsNullOrEmpty".

It would also be helpful to fuzzily match up names (better than no results): e.g. "isnowhi" should include "String.IsNullOrWhitespace" in the results (ranked below a possible "IsNowhereIncluded" method).

It would be great to be able to see the first/minimum version that a namespace is introduced. This way, if you are browsing and realize that you really only need .Net Standard 1.3 instead of 1.6, for example, you can see that quickly without having to flip back and forth. Alternatively, having a feature comparison chart where 2+ .Net versions are selected and their namespaces are compared would serve the same purpose.

On the documentation organization\navigation topic, one way of doing the documentation that is used for some product in Azure is the learning map\path (example: https://azure.microsoft.com/en-us/documentation/learning-pat...). I just LOVE that approach, it's visual, it's clear, you know where you are and where you are going, it's task oriented: it's perfect.

While the offline viewing option is great, PDF's "baked in" page format makes reading on mobile devices very cumbersome. I suggest offering downloads in open ePub format for easy reading on mobile devices -- allowing for text reflow, text and margin adjustment, color themes, etc.

For example, in the existing MSDN documentation for IEnumerable<T>, we also see all of the extension methods that are defined for that type:

https://msdn.microsoft.com/en-us/library/9eekhta0(v=vs.110).aspx

In the new .NET API Browser, the IEnumerable<T> reference only lists the GetEnumerator() method. None of the documentation for IEnumerable<T> says anything about the presence of these extension methods or even links to System.Linq.Enumerable.

https://docs.microsoft.com/en-us/dotnet/api/System.Collections.Generic.IEnumerable-1

Would love an API for programmatically searching for content.

Based on keywords, expose articles in either xml or json so third party apps can integrate documentation.

The date in article headers is great, but can it please be localised (e.g. dd/mm/yyyy in the UK) rather than assuming US-format dates?

The current doc format has 2 navigation panes on the sides and the content in the center. I use sometime the nav. pane on the left but never the one on the right so i'd like the option to hide it since it makes the center section (with the core content) too narrow.
The ideal would be the option to hide both so that if user want he can focus just on the content and have all the space dedicated to it. Thanks

Right now Monitor.​Wait is displayed as:

Monitor.​Wait(​System.​Object,​System.​Int32,​System.​Boolean)

Much easier to read version would be:
Monitor.​Wait(object, int, bool)

MSDN docs have a "Version information" section which says in which version a type or member was introduced. This is important information and should be included on the new site.

https://github.com/projectkudu/kudu/wiki

Add a section in the documentation that explains how to enable long path support with nuget.exe commandline tool and .net 4.6.2 - the idea is to add a nuget.exe.config file to same directory as user has nuget.exe located and then add the following to the nuget.exe.config (requires .NET 4.6.2 installed on machine running nuget.exe):

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.2" />
</startup>
<runtime>
<AppContextSwitchOverrides value="Switch.System.IO.UseLegacyPathHandling=false;Switch.System.IO.BlockLongPaths=false" />
</runtime>
</configuration>

Finding the right article is much too hard on docs.microsoft.com. For example, searching for Server Manager (in Windows Server 2016) brings up 36 000+ results, with the first page all about SQL Server. It should now be possible to filter the results based on product so that I get to Win 2016, or whatever.

The native scrollbar may be light and high contrast with the background. It's quite disturbing.

There are lots of comments on the site that, whilst not harmful can be dangerous.

Take this page for instance:
https://docs.microsoft.com/en-gb/dotnet/articles/visual-basic/

There are a couple of comments by a user attempting to submit XSS content to the page.

There should be an option to flag such comments as spam.

Thanks, Dan