Great! Shame we're going to break the apis ;-)
So a couple of points - * the app template loader would probably have seemed less tedious than the full path thing. Ie just 'templates' in the app directory. Things that might be worth showing in a slightly longer screencast: Templates: * Template errors (identifying the tag that went wrong), also looking at the backtrace of a normal 500 error * Template inheritance - this also would have helped you write valid html ;-) * Making a simple template library, eg a filter, a simple_tag, and an inclusion_tag (this would probably be easier if we documented those ;-) Views: * Writing a simple view with minimal processing using render_to_response Admin: * Edit inline * Overriding the template to customise your admin, maybe for a particular app * Validation errors * Automatic documentation at admin/doc/ .
