Now the best method I've found for finding content on msdn is a google search. If this no longer works my UWP interest will probably not be worth the bother.
Introducing docs.microsoft.com
91–100 of 195 posts
Re: Introducing docs.microsoft.com
#92Earlier quoted context omitted.
Use NoScript or equivalent to block scripts from the domain fyre.co. This prevents that annoying menu from popping up.
> Livefyre: The Leading Content Marketing and Engagement Platform Looks like something to block regardless of whether it creates annoying menus. Is anyone else a little surprised (and perhaps repulsed) by Microsoft putting semi-shady 3rd-party scripts like this on their site? This seems completely opposite of what the Microsoft I knew would do.
Re: Introducing docs.microsoft.com
#93Re: Introducing docs.microsoft.com
#94Oh no. It pops up a quick menu when I select text, like Medium. The problem is that I'm constantly selecting the lines I'm reading. :( Edit: Also, it's extremely narrow. On my 32" 4K display, 70% of the screen is empty. And the font is too think. And stuff keeps moving/jumping when I'm moving the mouse cursor. I want 1998 back.
> On my 32" 4K display, 70% of the screen is empty. Totally agreed on your other points (particularly about animations on selection) but as the article mentions, eye tracking repeatedly shows people have trouble reading very wide text. Also many people use large monitors to have multiple windows, rather than a single window maximised.
Yes but to optimize for larger screens, the correct thing to do is to scale everything up (fonts, spacing, etc) in a responsive manner.
The amount of text content per line wouldn't change much, it would just fill up the screen better instead of using the same tiny font size you'd use for a 13inch screen @ 1080p on a 32" 4K display.
Re: Introducing docs.microsoft.com
#95Nice to see MSDN move to more modern design. But I don't see any search capability? Shameless pug, We currently working on documentation hub for developers https://www.docsapp.io/
-what flavor of Markdown do you support (captions/TOC/auto-number figures and tables)
-can I paste images from the clipboard directly into the editor (like one can with github issues)?
-what's the advantages over setting up my own git repo and using something like gitbooks?
....
You _really_ should have a demo available for people to try out.
Re: Introducing docs.microsoft.com
#96Earlier quoted context omitted.
> On my 32" 4K display, 70% of the screen is empty. Totally agreed on your other points (particularly about animations on selection) but as the article mentions, eye tracking repeatedly shows people have trouble reading very wide text. Also many people use large monitors to have multiple windows, rather than a single window maximised.
> eye tracking repeatedly shows people have trouble reading very wide text Yes but to optimize for larger screens, the correct thing to do is to scale everything up (fonts, spacing, etc) in a responsive manner. The amount of text content per line wouldn't change much, it would just fill up the screen better instead of using the same tiny font size you'd use for a 13inch screen @ 1080p on a 32" 4K display.
When lines get longer you either have to increase the leading, or font size, or shorten the lines to retain readability. Personally I hate having to detach every other tab from the browser just to change to width to something that's readable. In that sense I much prefer the content to have a maximum width beyond a certain viewport width because it's the only viable option to still have text that is readable.
Re: Introducing docs.microsoft.com
#97Oh no. It pops up a quick menu when I select text, like Medium. The problem is that I'm constantly selecting the lines I'm reading. :( Edit: Also, it's extremely narrow. On my 32" 4K display, 70% of the screen is empty. And the font is too think. And stuff keeps moving/jumping when I'm moving the mouse cursor. I want 1998 back.
If it were 100% wide on 4K, how would your eyes scan the text? It's useful for illustrations (graphics), but I haven't met a person yet who can read wide text as efficiently as one or more narrow columns.
Re: Introducing docs.microsoft.com
#98I think the main issue with documentation for Microsoft products/APIs is that the content is spread out on a large number of different Microsoft domains which makes it inherently difficult to find something. I have also often found (after using google to find the relevant article) that the content is either out of date or not relevant anymore. Adding yet another site to the list of sites which might or might not have…
Depending on what you're looking for, there's usually only two you need: MSDN[0] and TechNet[1]. [0] https://msdn.microsoft.com/library [1] https://technet.microsoft.com/library/default.aspx
"usually"
"only two"
That means that Google.com is still needed as the front-end to MS documentation. Ergo, it doesn't matter how many domains they use to host their documentation.
Re: Introducing docs.microsoft.com
#99But there is really important knowledge out there regarding ease of reading, contrast, ideal formatting, etc.
Cant believe that they choose a font weight that is so light. That alone makes this redesign way worse than the original.
Re: Introducing docs.microsoft.com
#100Yikes. Seems that almost no one designing websites bothers to study the more important parts of typography. Recently, typography has been bastardized to mean "an expensive looking sans serif font." But there is really important knowledge out there regarding ease of reading, contrast, ideal formatting, etc. Cant believe that they choose a font weight that is so light. That alone makes this redesign way worse than the…