Why not make two screencasts (or more)? For example: 1) Blog+RSS+flatpages with nice post editor: Admin + RichEdit (either ours or 3rd party like TinyMCE). 2) Adding comments + secure e-mail form to the blog from 1st screencasts with Markdown/Textile/Whatever (or restricted RichEdit, if we have it by then).
Both parts are rather smallish. I think a series of 5 minute episodes will be better for people to digest than one big movie. And it will build a real application in the end with all niceties you may possibly want. Another idea is to reserve at least a minute per episode to showcase what we actually built: people need time to soak in and appreciate all available features. Thanks, Eugene "Simon Willison" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > > On 21 Nov 2005, at 09:45, James Bennett wrote: > >> 2. Django doesn't have one of those nifty "useful application in >> twenty minutes" tutorials/screencasts. Again, I'm partial to a weblog >> as the sample app because it's stupidly easy to do in Django and shows >> off a lot of the nice built-in stuff, and having something visual that >> people can watch would go a long way toward communicating how simple >> and effective Django really is. > > If we're going to have a weblog building screencast, we should make sure > it's unbelievably short - definitely less than 5 minutes, preferably less > than 3. If you think about it a basic weblog app is nothing more than a > single simple model, the date-based generic views and four templates. > > It would be nice if we had some way of speeding up template creation for > generic views... then we could get it down to less than a minute :) > > Cheers, > > Simon >
