I don't think that's a problem to be solved by the core documentation - rather it's the role that tutorials, howto's etc solve - taking you from 'what' to 'how'.
Maybe the Django docs should guide people to a few more of these before hitting them with the authoritative docs.
A tutorial and a book solve completely different problems. A tutorial will only help you if you know what you want to achieve, and can therefore search for the tutorial. You read a book to find out about functionality you didn't know was there, lest you need it in the future.
An organized approach to "here are all the things we do" is definitely appropriate for the core documentation.
Maybe the Django docs should guide people to a few more of these before hitting them with the authoritative docs.