For the sake of shameless self-promotion, I'd also like to suggest my book for anyone who feels Discover Meteor moves a bit too fast: http://meteortips.com/book/ (It's free.)

:)

Thanks so much for this. I finished your book over the weekend and loved how clear and concise the writing was. Discover Meteor was difficult to follow as a beginner but am more confident that I can follow along now. Thanks again!

http://www.meteor-tutorial.org/ - highly recommended by me because I wrote it.

Discover Meteor is great but it left me wanting for some more, in-depth resources. I found the Meteor in Action book to be of great help. They are about to release the complete version but the Early Access version is pretty much done: http://www.manning.com/hochhaus/

Why aren't these great books turned into the official documentation if the current official docs are lacking in so much quality?

The official docs are great for the core APIs. I agree more attention is needed for Blaze and Spacebars. But lacking? No.

The source code is very well annotated also.

Because that sort of "consulting economy" is the open source business model de jure.

It's not really new, except perhaps it being more indie now. In most (but not all) niches over the years, the paid, formal published for-profit books have provided the best documentation, right back to the 70s, through O'Reilly's catalogue (he got rich for a reason), through MSDN, and right up to now. Indeed, it's possibly better now because a single author can do it all on their own.

Just FYI: du jour. De jure means something else.