<story><title>Introducing .NET Core Docs</title><url>https://docs.microsoft.com/teamblog/introducing-net-core-docs/</url></story><parent_chain></parent_chain><comment><author>haft</author><text>This is so much better than the old Technet approach.  I especially appreciate the UX that went into creating the site - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.microsoft.com&amp;#x2F;teamblog&amp;#x2F;introducing-docs-microsoft-com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.microsoft.com&amp;#x2F;teamblog&amp;#x2F;introducing-docs-microso...&lt;/a&gt;&lt;p&gt;Is there any change this will be available as an option for local documentation from VS?  Sandcastle is a little dated.</text></comment>
<story><title>Introducing .NET Core Docs</title><url>https://docs.microsoft.com/teamblog/introducing-net-core-docs/</url></story><parent_chain></parent_chain><comment><author>jc4p</author><text>I know it _just_ launched but oh my god how do you launch such a slow site. I&amp;#x27;m trying to load the &amp;quot;System.Drawing&amp;quot; API docs and Chrome inspector just shows a GET pending alongside a _lot_ of analytics and marketing calls being made. I waited to see how long it&amp;#x27;d take, 30s to load the page: &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;i.imgur.com&amp;#x2F;Z6y1ulSr.png&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;i.imgur.com&amp;#x2F;Z6y1ulSr.png&lt;/a&gt;&lt;p&gt;Anyway, ignoring the launch issues: My #1 annoyance with MSFT documentation is sub-classes being on a different page. If you want to call a DirectX method which takes 4 inputs, you need to open up a new tab for each of those inputs to see the possible values &amp;#x2F; etc. I hate it, very very much. I hope their new documentation doesn&amp;#x27;t have this issue, I&amp;#x27;ll check back again in a few weeks to see if I can actually load pages on this site.</text></comment>