The problems with nanoc unfortunately only become apparent after you've invested significantly into it and your site starts to grow in complexity and/or size (file-count). I've been there and it wasn't fun at all...
The first problem is the obscure Rules DSL. It feels somewhat elegant in the beginning when you're mostly working of the canned examples. But once you divert from the beaten paths it quickly turns into a hairy mess and you find yourself with a >300 lines rules file, various workarounds tacked into the 'preprocess'-block, a conglomerate of "filters" and "helpers", and a rapidly fading memory of "How did all this fit together again?".
The second problem is performance. If your site contains auto-generated parts (e.g. API-docs) then the number of files may quickly grow into the thousands. Nanoc doesn't cope well at such sizes. In the end the compile-phase took 10 minutes(!) for my ~9k file-project on a beefy machine.
That said, nanoc is okay for smallish projects, just beware the constraints.
Middleman has been a more pleasant experience here (after the porting pains). It's a much more straightforward design. I can come back to it after a month or two and be immediately productive again. With nanoc this always involved a lot of pain re-learning the Rules-magic and interdependencies...
I'd recommend to look at the "community templates" (linked from the MM-site). The "HTML5 Boilerplate"-template had nearly everything covered that I was interested in (I only swapped out 'suzy' for 'less') and since MM is such a simple design it really only took a few hours to feel at home.
So I made the classic mistake and built a Node.js Jekyll clone -- there are a few other static site generators in Node, but none used the exact same file structure as Jekyll (unless I missed some, which is entirely possible).
It now handles most Jekyll sites I've tested, including Mojombo's:
`npm install -g enfield`
Supports plugins as well. Patches welcome!
Also life happens while making other plans.
So I welcome the announcement and I'll be super happy once umpteen long-waiting pull requests are processed.
But somehing tells me, don't hold my breath.
You're safe to hold your breath. ;)
One thing that Jekyll needs to improve is the process for getting a blog up and running quickly. I turned to Octopress for that (being a Jekyll "framework") but I think it's an function Jekyll itself could provide for.
I'll have non developers creating and maintaining pages and posts, so I'm hoping I can build an easy workflow with just Jekyll and a bit of prose.io. I've not found any sort of site generator/convertor that's geared for use by non-developers.
Our workflow included Github, the Github desktop clients, SublimeText 2, and a script we wrote which would run `jekyll --auto --server 3000` so that the person making the changes could ensure that it came out the right way before committing to the repo. Pretty easy stuff.
Hopefully this'll help spur Octopress dev, too.