I would like to promote this issue to put it on the Roadmap for the next release. There is still a huge amount of 1.7.x user doc content that is not in trunk docs. I have not even looked at the developer docs discrepancy. It concerns me that we are at 2.0-RC1 and we are still missing many features (in that they are not documented on trunk). Users still need to read 1.7.x and trunk side-by-side.
Mike and Alyssa, the new docs you have written are excellent. They must have taken quite a while. Some of the 1.7.x docs are more textual and do not require new screenshots, just some proofing and updating. These could be delegated to the original authors or knowledgeable volunteers. We can make these subtasks.
If you agree, we could promote this issue to:
Fix version: 2.0-RC2
We need it to be Critical to block release. We need it to be fix-version on a release tag for it to appear on the radar. Fix-version on a branch will be invisible.
It is time to start hassling all module maintainers to get some better docs. I am as bad an offender as any. Good docs make a huge difference to end users. Check out the latest PostGIS docs. Inspirational levels of improvement, and better than any commercial competitor. As good as PostgreSQL. Sphinx lets us do just as well.
Documentation is not what developers like to do, so you need to crack the whip.