-What happened to the comments? That was one of the most useful features of the old documentation, and I constantly relied on them to find examples or clarify edge cases.
-The code samples are on opposite colored backgrounds, which makes the whole page extremely painful to read. Can you imagine reading paper book that had code samples written in white text on a black background? How is that a good idea on the web?
-The huge blue border around the edge adds even more visual noise.
-Why is so much stuff laid out inside of boxes, starting with the list of functions? Developers are experts at reading raw blocks of text, so minimal formatting is needed.
-Finally, where did the old documentation go? The content has been changed, but where can we find it? There doesn't seem to be any links.
The old documentation definitely needed some work, but these improvements have brought with them new problems, and overall I find it harder to use than before.
While not perfect, it does a lot of things right: no extraneous formatting around the page edges, solid background, clean code examples, and importantly, access to old versions of the documentation.
After experiencing the wall of well-intentioned garbage that is php.net I no longer like comments in docs. Those examples and clarifications of edge cases should be in the documentation itself.
And how do you discover these edge cases if you don't have comments? The point of the comments is to point out common issues, use cases and potentially, common misunderstandings.
I have good eyesight, but I have a hard time reading the grey text between the strong code examples in the expressjs documentation. Also, the visual border around the examples is too subtle for me. I may look nice and fresh, but its just plain hard to parse visually. Certainly not a good example.
-What happened to the comments? That was one of the most useful features of the old documentation, and I constantly relied on them to find examples or clarify edge cases.
-The code samples are on opposite colored backgrounds, which makes the whole page extremely painful to read. Can you imagine reading paper book that had code samples written in white text on a black background? How is that a good idea on the web?
-The huge blue border around the edge adds even more visual noise.
-Why is so much stuff laid out inside of boxes, starting with the list of functions? Developers are experts at reading raw blocks of text, so minimal formatting is needed.
-Finally, where did the old documentation go? The content has been changed, but where can we find it? There doesn't seem to be any links.
The old documentation definitely needed some work, but these improvements have brought with them new problems, and overall I find it harder to use than before.
Edit:
Compare Google's documentation: https://developers.google.com/maps/documentation/javascript/...
While not perfect, it does a lot of things right: no extraneous formatting around the page edges, solid background, clean code examples, and importantly, access to old versions of the documentation.