> 1. it's indeed very complete, but we need time to get the information > we want. > 2. it's lacking a "Getting started". > 4. Also demos are missing. I think they should be merged with the > documentation. The mootools.net/docs are API docs. It's not a guide. That's why there is no 'Getting started' section and that's why there are no demos.
> 3. There is no quick reference: when we click a class on the left, all > the methods are shown on the right and all their associated > documentation is on the same page. As an index page for a class, it > would be nicer to list all the methods from it, associated with a > little explanation (like on php.net). I don't really see this point. When you click on a Class, all methods are mentioned on the right, clicking that gets you straight to the explanation. > 5. There is no categorized topics. The structure organisation only on > the classes structure. For instance, the Element class has too much > methods for a human to reasonably make it looks good in his mind. > Maybe some categories like on the jQuery documentation would be nice > (attributes, traversing, manipulation). The documentation is categorized the way MooTools itself is categorized, by modules/packages (whatever you want to call them). This is also because they're API docs. You get to pick the modules you want, and use those, and you'll find the documentation for those modules right where you'd expect them. Perhaps taking a look at http://mootools.net/core will clear things up a bit. I do agree that this doesn't help people who just want to download MooTools and use it with plugins X, Y and Z. But then another question is whether those people are MooTools' target audience. Like Arieh mentioned, for more guide-like explanations, mootorial.com/wiki is a better starting point. Tim.
