Many of the topics are very poor documented or documented with meaningless information which can be understood from the name of the class or property.

Please , make the website User Friendly.

The code looks terrible , because it is in black color . Why aren't you using any syntax highlight ? Look at the other sites with c# or any code . They highlight the CODE , and then it becomes readable.

This website is good , and the tutorials and examples are awesome, but the fact that there is not SH , makes me skip msdn.com website and look for another page.

Date stamp all articles in order to make it easier to know how how fresh the information is.

The tree on the left always reflects incomplete info on the topic. I use Google to search MSDN. As an example, why are these in different places?

http://msdn.microsoft.com/en-us/library/hh510230.aspx
http://msdn.microsoft.com/en-us/library/dn135328(v=sql.110).aspx

Examplain and Give Code examples with screen shots. In the examples there are steps and code deployment which are lack of screen shots. The screen shots (output result) should be also there.

MSDN Site should responsive site, as your microsot.com site is.

Make Full MSDN Library available OFFLINE (as it was before).

All too many MSDN articles contain links to internal Microsoft documentation that are no longer valid. I realize this is a Sisyphean task given constant changes to MS web structure, but it is critical nonetheless.

It will be nice if there is an option attached to every sample program that is provided in the documentation, so it comes handy to check the results by oneself

Please make a settings at MSDN site to never ever ever display articles translated to Russian or any other language.
I'm Russian but it is very hard to read articles that were translated to Russian.

The example given gives an idea. But how this concepts are applied in some real life concepts please explain.
and give some programming examples that uses all the oops concepts together in a particular program.

Please add screen shot because "Picture is more than 1000 words".

When I visit a Library article I would like to see other related articles within the Library. Very often I find the reference docs, but then it's difficult to find more conceptual articles, or vice versa.

Where content is declared to be retired, it would be great if it was listed as obsolete or provided links to updated\superceding content.

Add simple code examples with sample inputs and sample outputs like if you were explaining it to a baby or a non-technical person.

This is new but...provide screenshots with examples

specific commonly used functions, methods, ways of doing things so that learning C/AL code becomes easy not hard......