I think the Django tutorial is an excellent piece of documentation. If somebody doesn't have enough patience to work through it, they probably won't have the time to read the rest of the docs either and will most likely end up writing messy code.
There is a reason most tutorials start with: this is how you show something, and if you want to sawe data here's how to make ane use a database. Sure doing it the other way around seems natural to you and other web developers, but it's a bad way to introduce a framework to a complete newbie.
Making the first step simple will just make it even more frustrating later when they don't understand concepts like objects, modules, packages, inheritance, DRY, separation of concerns, best practices, yadda.
Any programmer should be able to write down a minimal example of whatever they're working on, but personally I had never thought through how to make a minimal django app -- had you?
For one, Django isn't a micro-framework and using it as such, although possible, is probably overkill.
Anybody who has ever seen an MVC pattern or read about it will understand why it needs 6 parts and won't necessarily be intimidated by it. I know I wasn't when I first looked at it.
On-boarding new users needs to be simple and welcoming, nobody disputes that. But this trend in dumbing down everything should not extend to web frameworks in my humble opinion.