I wanted to bring up an example that uses Blogofile in a slightly unconventional manner and see if I'm thinking about this the right way. Let's say you're a movie buff and you're making a site that's going to host your movie reviews: Moviefile. 1.) When you write posts, some (but not all) of your Moviefile posts will correspond to reviews about individual movies. You'll also have generic posts that reflect your general feelings about, say, the movie industry in general, topical news, et cetera. 2.) Posts may have a `movie` hash in their YAML preamble. This is a hash of three key-value pairs: `year`, an integer representing the year the movie was made; `rating`, an integer score for the movie from 0 to 100; and `_title_`, a string representing the movie's name. Posts with this hash are considered reviews for the aforementioned movie. 3.) You'd like a movie_index.mako, so that you can have a page which is a list of every movie you've reviewed so far with _link_s to posts about that page. Ryan had a good example here for how you'd make a category_index page: http://gist.github.com/244820 (I think there is a slight typo above, though: `category_indexes.py` should be named `category_index.py` or else Blogofile won't associate it correctly.) Presumably you'd just pull the same sort of stunt here

Implemented: http://github.com/EnigmaCurry/blogofile/commit/06009403428d9ca1d16376... Btw, I merged templates-externalized branch back into master. The master branch is now on track to become the 0.6 release.

The docs already have this here (http://www.blogofile.com/documentation/file_overview.html#yaml-header), but it looks like it's missing a few things, like the format attribute that the `simple_blog` demo posts use. I updated the docs here: http://www.blogofile.com/documentation/file_overview.html#yaml-header I've still got a lot more work though to document all the changes since 0.5