But when I'm writing a blog post and I constantly want to preview it in the browser (since lots of my posts have images and such I prefer seeing the real layout than purely in sublime text 2) I use a rake task I have that stashes every post but the one I'm working on so it only generates the one post.
Edit: and a faster generation time means I don't have to feel bad using lots of liquid filters / includes (which can help clean things up and organize my site).
Two things I'd like to see (which I've had to fork my jekyll for) and that I'll put on the github:
- "multiviews" support (it's how I get all my links to have no .html ending, well that and some rack:rewrite rules)
- support for different post types that are not in the main site.posts. I only have 2 types now but for a while had a regular post, a shorter "aside" style post that was not in the main feed nor homepage and had its own index and feed, and another post type for photos. These go beyond just different layouts. Though this is more of a CMS feature than a blog feature which may be a direction thing that Jekyll is not intended for. ?
I fail to see how changing a typo in an article's content would require the whole thing to be rebuilt. Even adding a page would not require rebuilding every single page unless the new page appeared in a global navigation. Building the dependency graph automatically could even turn out to be not that hard.