Name is almost as good as a great Brazilian django course, by the genius Henrique Bastos, called Welcome to the django: http://welcometothedjango.com.br
I didn't get it when Google decided to name their language Go because it was awfully hard to google. Same here : the name isn't bad but will be impossible to google for anyone forgetting to add "python" to their request.
Anyway, great initiative, I'm looking forward to read it ! (star or bookmark it if you intend to find it next week) :)
+1 for anyone that takes the time to put stuff like this together.
With that said a cursory glance at the material raised a couple flags with me when I got to best practices...
Keeping in mind this tutorial is an introduction I think it would be really great to include the following:
1. Settings module in the project module with a simple example with base settings that can be extended/overridden with a local settings file. I've never worked on a Django project where this isn't needed and think it's a very good "best practice" that should be addressed.
2. Even if it is personal preference I do not think the slide detailing app specific templates in a project level template directory should be included. To spend time making code subdivided in to distinct application logic it doesn't make sense to have the templates excluded which reduces the portability / reusability of the app. Django contrib app structure (especially auth/admin interaction) is a good example of Doing It Right™ (or at least in the spirit of doing something right :)
I've used Django before, and I found it disappointing. Does the ORM still lack identity mapping? Does it still not let you run custom SQL and get the results back as model objects (instead of plain tuples)?
