41–50 of 195 posts
Maybe I'm just losing my eyesight, but does anyone else find that font impossible to read?
At $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…
Situation: There are 14 competing information stores. 14?! Ridiculous! We need to develop one universal store that covers everyone's use cases. Situation: There are 15 competing information stores.
I would prefer if MS opened up their documentation and made it available for offline usage. The current options for that are hopelessly inadequate with (arbitrary) limits on the amount of data you can export. Now we get this crapscript laden fancy thing with only content from the marketing division. Not impressed.
Azure? git clone https://github.com/Azure/azure-content.git
Azure RMS? git clone https://github.com/Microsoft/Azure-RMSDocs.git
...
Also, the marked-text context menu: that only works within a single paragraph. Cross over to the next and it's not showing any more.
At $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…
Situation: There are 14 competing information stores. 14?! Ridiculous! We need to develop one universal store that covers everyone's use cases. Situation: There are 15 competing information stores.
Sometimes you have to push to fix the process
From 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…
This makes no sense at all, even if you think people's attention spans have shortened. You see the same amount of content at once regardless of whether it's been paged, unless your browser window is ridiculously large or the content has been literally split into paragraph-per-page levels of fragmentation. You'll eventually get to see all the same content, but you have to spend more clicks (and possibly scroll) to get to the part you want instead of just scrolling. I have the same gripe with some other sites that love click-toggling sections (especially when there is no "expand all" button, or expanding one collapses the others, or even worse --- they default to collapsed without JS.)
Maybe it's the result of some stupid "engagement" metric that awards clicking around? That's completely counter to the point of documentation; it's not supposed to require much interaction, it's supposed to be something you passively read while doing whatever it is you need to with the information you've consumed.
Nice, I've always found msdn to be a bit hard to navigate through.
Yes! When the easiest way to something on a web site is to ask Google (or some other search engine) for it, something is very wrong.
Oh 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=...
It goes to the right of the paragraph in that case instead of the last sentence of the paragraph.
Oh 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.
http://web.archive.org/web/20111228110049/http://msdn.micros...
http://web.archive.org/web/20130422112102/http://msdn.micros...
http://web.archive.org/web/20150102192514/http://msdn.micros...
I very much prefer the first design too.