Nice, I've always found msdn to be a bit hard to navigate through.
Introducing docs.microsoft.com
11–20 of 195 posts
Re: Introducing docs.microsoft.com
#12So, will I have to login into something to read the docs now?
Re: Introducing docs.microsoft.com
#13Interesting choice of domain name. Coming from docs.google.com, I almost thought this was Office 365.
Also, docs.com. A Microsoft product.
Re: Introducing docs.microsoft.com
#14From TFA: "Shortened Article Length Another common piece of feedback was that our content at times can be overwhelming because of its length and that long articles are more difficult to navigate and find what you’re looking for. To address this, we’ve broken down many longer articles into smaller logical steps and provided Previous and Next buttons at the bottom of articles to navigate between steps in a multi-part t…
Their solution appears to be actually worse than the initial state, if they simply automatically split the long pages and add "prev - next" buttons.
The proper solution for them is to look at Wikipedia as an example. Tables of contents in longer articles, manually introducing the new topics or reorganizing when it's reasonable. And it's not something that can be automated.
Automatic splitting of long pages to shorter ones is good only for "we get money for clicks" media but not for a repository of knowledge with serious intentions.
Re: Introducing docs.microsoft.com
#15Oh 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.
>I want 1998 back.
I'd be happy with 2011, just before the Metro-inspired redesign of MSDN hit.
Re: Introducing docs.microsoft.com
#16Oh 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.
Also a small "add comment" icon pops under each paragraph when hovering, making entire paragraphs jump up and down as I scroll down the page, it's very distracting.
Re: Introducing docs.microsoft.com
#17Are they going to fix the page load times? MSDN is terrible for click-wait-scroll usage, especially if you're trying to use the left navigation drilldown.
Re: Introducing docs.microsoft.com
#18Oh 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.
> And stuff keeps moving/jumping when I'm moving the mouse cursor.
Yes it's quite bad on that blog post, but if you check out an article [1] it doesn't suffer from that problem. Still has the selection-reader [2] problem, though.
[1] https://docs.microsoft.com/en-us/remoteapp/remoteapp-whatis
[2] https://blogs.msdn.microsoft.com/oldnewthing/20150528-00/?p=...
Re: Introducing docs.microsoft.com
#19Maybe I'm just losing my eyesight, but does anyone else find that font impossible to read?
Re: Introducing docs.microsoft.com
#20At $DAY_JOB we have various document (or rather, knowledge) repositories -- a mostly-abandoned-but-still-useful-often-enough-to-not-ignore wiki, the obligatory but overwhelming salesforce, personal (silo) collections of email lists/archives, a semi-public knowledge base, a half-hearted attempt at moving internal mail lists into yammer, various product guides (PDF's), a public-access user forum, an LMS, and probably a few others I don't know about. It is precisely as easy to search for information as you'd assume.
Last year we embraced Sharepoint - with expectations of replacing much of the above. (It didn't.)
Evidently no one uses Sharepoint as a way of presenting documentation to the world - let alone using the wiki-like features - not even Microsoft. What's the opposite of NIH syndrome?