Anyway, great initiative, I'm looking forward to read it ! (star or bookmark it if you intend to find it next week) :)
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 :)
We will be starting a public facing workshop in the next coming weeks, you can check it out at http://www.theymc.com/.
I will definitely try get some recorded screencasts up for those of you not in Toronto.
Is this basically a self-paced, self-taught series of notes?
Either way, looks like a nice resource, so thank you.
We're looking to make screencasts of the upcoming public facing workshop (www.theymc.com), and open them up to everybody.