For starters the current console development pipeline is broken because the Android SDK Tools does not support Ant from 25.3.0 (see). It is a major development pipeline for cocos2d-x but all attention is now on CocosCreator and other developers who were using or starting out to use console/ant projects are left in the dark. Only way to make it work is with the tools_r25.2.5-windows replace hack which is only mentioned in a couple of github comments -> add this to the documention until console pipleline is fixed/upgraded to clang or solved otherwise.
The Wiki has very many deprecated/useless pages… Remove them because these sorts of learning materials often instantly turn away a developer. Empty, empty. The SDK Integration main tab has only Facebook in it, this tab should be removed altogether because it implies that there is support only for Facebook. Cocos Studio, Cocos Code IDE are not developed for a long time time, why are they there as main tabs in the wiki?
There are very many nicely composed example projects with Cocos, if you were to found some ways to link/integrate these into the documentation to a certain extent that would be great. Now to be more precise, I’d define the documentation as the Programmer’s guide and the API reference (Wiki is mostly useless, if not corrupting to be honest). So most of what I mention below is for the upgrade of the API reference. Since however that has a limited format, as it has to conform to strict html boundaries as laid down by doxygen, including the example projects would be best done in the Programmer’s guide. Still, links in the API ref to the Programmer’s guide and vice versa would be very helpful. There are many mechanics in Cocos that are pretty hard to figure out how to work with because documentation(API ref) doesn’t have but the inheritence trees and member information on them. The developer is required to dive into the engine source code and analyze examples if the Programmer’s guide doesn’t talk about it.
I think the documentation for a long while has been in need of a general upgrade. There are a lot of erronous texts, gramatically. Now that I’m mentioning this, even on the main page, Programmers guide should be either Programmers’ guide, or Programmer’s guide, the latter might be better. Additionally all modules and classes that are designed for public usage should have a brief description on them, at least 2-3 meaty sentences.
All in all, most example projects should be referenced in the documentation (API ref/Programmer’s guide) in at least one place. All classes directed at public usage should have descriptions on them that mention how to use them, not just what they are (or what they seem like). And lastly, try to contain the grammatical errors. If these took place, Cocos would be a much friendlier engine to study.