I concur, wholeheartedly. I purchased the 2.32 manual when I was learning Blender, because it was the only documentation that I could be sure was complete. I found it frustrating when I was working through the tutorials, only to discover that part of the tutorial was either missing, marked with *TODO*, or piecemeal.In my opinion it would be better to have a completely new manual.
There are so many reworked areas in Blender since 2.32 version that I think it would be hard to explain in a separated document all the changes. This can be frustating, expecially for a newbie that wants to learn the software properly.
I realize this probably isn't the case anymore, but my suggestion is to create documentation in a tutorial-like format, for beginners. Highlight ALL of the features of Blender (not just the commonly used ones) in a tutorial, then have separate chapters for each specific topic (eg. materials, textures, animation, etc...). From the tutorial, there could be links to the other chapters, if the newer user wanted more information.
Also, I think it's necessary to put some amount of computer graphics theory into the discussion. The paper manual provided this fairly well. I just think that for someone to completely understand how to make animations, for example, they should understand concepts of frame rates and how the computer interpolates between key frames.
So, my suggestion is to build the following sections of documentation:
1. Thorough Tutorial of all Blender features
2. Chapters on all Blender features, going more in-depth
- Each chapter will include some sections on computer graphics theory
Obviously, much of the documentation does not need to be re-written. Since almost all of the 2.32 documentation is present, as well as much of the documentation from 2.41 and beyond, we wouldn't need to re-write all of it. Ideally, I would like to participate in this project and document the thorough tutorial of all of Blender's features. I'd like to create a nice looking scene and/or animation, and then go through how to construct the scene. This would give new users a sense of having accomplished something at the end of the tutorial.
I have done much documentation in the past. (You can check out http://portal.aero.und.edu - I did most of the documentation in the DebianLinux section), and I am very good at writing tutorials. I enjoy writing, and I think that if we have a number of people working as a team, we can get some great documentation going.