Earlier quoted context omitted.
I too am a highlighter.
I too am a highlighter. We should form a self-help group.
rethgilhgih a ma oot I
Introducing docs.microsoft.com
171–180 of 195 posts
Re: Introducing docs.microsoft.com
#172Re: Introducing docs.microsoft.com
#173From 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…
[Disclosure: I work for the team that built docs.microsoft.com] Thanks for the feedback, and we went through a lot of customer feedback already on this. I'll try to be brief in a response - A good example on why - For our documentation we clearly saw customers jumping around content trying to find the part of the article that helps them. Depending on the article (see point #2) very few people read from beginning to e…
One thing I beg of you:
Don't break links to old versions of documents!
(I realise this requires building a redirect forest. But we're talking 20 years of MS documentation.)
Re: Introducing docs.microsoft.com
#174Earlier quoted context omitted.
What type of panels and implementations (monitors sold) work well in portrait mode? I've tried it once and I saw an odd pattern that wasn't very comfortable to look at.
TN panels are usually horrible, as they have (in landscape mode) a very limited viewing angle up or down before colours start to shift or parts of the screen appear way darker than others. IPS panels should work without a problem in both landscape and portrait mode.
I use IPS and VA panels, but I wouldn't be able to tell what panels it was when I had the bad experience. I'll try it again, but not every IPS or VA panel is good either.
Re: Introducing docs.microsoft.com
#175yes we live pastels and hipster fonts.
We've asked you before to stop posting uncivil and/or unsubstantive comments to Hacker News. If you keep doing it, we'll ban your account, so it would be much better if you would stop doing it.
Re: Introducing docs.microsoft.com
#176Earlier quoted context omitted.
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.
Solution: Move things over from one into the blessed solution, and then kill the other one. Repeat as necessary. Accept that nothing will cover 100% Sometimes you have to push to fix the process
Quite often the only push that can fix problems like this is push from upper management because no matter what someone is going to be upset and will sabotage or drag it out forever.
Re: Introducing docs.microsoft.com
#177Earlier quoted context omitted.
[Disclosure: I work for the team that built docs.microsoft.com] Thanks for the feedback, and we went through a lot of customer feedback already on this. I'll try to be brief in a response - A good example on why - For our documentation we clearly saw customers jumping around content trying to find the part of the article that helps them. Depending on the article (see point #2) very few people read from beginning to e…
One thing I beg of you: Don't break links to old versions of documents! (I realise this requires building a redirect forest. But we're talking 20 years of MS documentation.)
[Also MS employee that works on the docs.microsoft.com team]
No, we will not break links. We are doing graceful redirects from MSDN/TechNet to the new site.
Re: Introducing docs.microsoft.com
#178soo, the same thing as google docs but you have to pay for it..
Not at all. docs.microsoft.com is the documentation portal and has nothing to do with the online Office Word service.
Re: Introducing docs.microsoft.com
#179I thought biggest improvement to the MS website, MSDN and technet included, would be simply to disable the incessant demands for feedback on the webpage or surveys. Would you like to take a short 25 minute survey? You visited this site 25,000 times previously and we have asked each of those times, but maybe this time you will change your mind and answer the survey.
[Disclosure: working on the team that built docs.microsoft.com]
We are fixing that. Thank you for the feedback!
Re: Introducing docs.microsoft.com
#180My big problem reading Microsoft docs is the pattern (around Visual Basic docs?) where they put objects, properties, methods, functions, etc. in separate sections, making it hard to figure out what applies where. Are they planning to address the difficulty of getting information out of the structure at all, or are they just putting window dressing on it?
[PM on the docs.microsoft.com team]
Yes, we are planning to address content structure to make sure that all important reference and conceptual information is well-organized and accessible. If you have any particular concerns regarding this, feel free to shoot me an email: dendeli [at] microsoft