I've updated my mini-review of static-site generators to include it:<p><a href="https://github.com/skx/static-site-generators" rel="nofollow">https://github.com/skx/static-site-generators</a><p>Early testing looks good, but like so many existing tools it mishandles symbolic links.
<i>"Write rich web applications using the latest technologies without having to host your own node.js servers [...] No matter what plugins you use, the output will always be a static website you can host anywhere."</i><p>I don't think that's a very common definition of "rich web application".
I got scared when it said node.js, then I saw it was only using node.js for the customization part, not the hosting part and I got relieved.
I really think they should emphasize that you can use your own web-server, using node.js to host a static site just doesn't make sense.
It seems like just about everyone's written a static site generator. Mine is Kerouac (<a href="https://github.com/jaredhanson/kerouac" rel="nofollow">https://github.com/jaredhanson/kerouac</a>), another Node.js-based generator.<p>I specifically wanted to apply the middleware concept to generating pages, which turned out to be a decent fit. It ends up being a very similar API to Express, so its instantly familiar to Node.js developers. Check it out.
Really like this little framework, was just checking it out a week ago. To the author or anyone else interested, I'm making a little tool that does something very similar (<a href="http://roots.cx" rel="nofollow">http://roots.cx</a>) and am aggressively adding functionality in order to make almost anything feasible to build as a static site.<p>Would love to talk about this stuff any time!
Anyone else find it funny that a language originally designed to add <i>dynamic</i> content to the <i>client</i> side is being used to generate <i>static</i> content on the <i>server</i> side?<p>Makes sense to me though ... It's a natural fit for a front end dev who knows HTML/CSS/JS and also a good way to learn proper templating.