What's new in the Windows Dev Center part 2: MSDN Library integration

In our first What's new post, we discussed the new look and feel of the Windows Dev Center.  This experience would only be partially complete if all the documentation was presented in an older style. So, we worked closely with MSDN to improve the way that the "library" content appears on the developer center.  To compare and contrast, here is the older developer center experience:

This evolved into a "lightweight" experience which simplified the table of contents to address feedback that we were getting from customers that the table of contents was getting too long (vertically):

The lightweight experience evolved again into the experience we have today which moves the parent table of contents elements into what we've been calling the "breadcrumb" which appears on the top of the site and moving peer elements to the left side of the site:

Note that the navigation links on the top of the site no longer change to the library links.  This way, you know that you're staying locked into development resources for Windows rather than developer resources all up for Microsoft.

Some related changes have been critical to improving the experience in content such as the ability to integrate video into content (content coming soon!) and the new ratings control (we'll talk about this in another post).  But at a high level this was one of the most significant updates that we made in the center for BUILD.

See Also


Note that you still can use the "classic" look and feel for any content that appears in the MSDN library.  First, go to the MSDN library and navigate to the section of interest.  Next click the gear icon in the top right section of the page:

Next, change the preferred view to classic:

Thanks James for asking :) 


Update 2:


Jeff Braaten wrote a great blog post on how he and his team engineered the integrated library experience, or, "An MSDN Library for the Windows Dev Center". And also pointed out that the major benefit of the "Lightweight" UI for MSDN made a huge difference in how much real estate was available to the content area.