Static Site Generator Community Meeting (March 12)

[Colin Clark]

Hi Justin,

On Mar 12, 2014, at 10:32 PM, Justin Obara <obara.justin at gmail.com> wrote:

> Thanks Colin. Could you also add the reasoning behind the node.js criteria. You were talking about this at the meeting today but some audio issue made it hard to get all the details. 

I have updated the page with my thoughts about why it’s worth considering Node.js-based solutions ahead of those written for other platforms.

http://wiki.fluidproject.org/display/fluid/Static+Site+Generators+Research

The key point is this:

"A static site generator written in Node.js could be easily extended with features written using Infusion and other tools we already use every day (e.g. Grunt). Even more interestingly, we might consider the long-term possibility of integrating static site generation features into Kettle, so that developers could easily deploy blended sites that consistent mostly of static HTML but also include JSON feeds or some dynamically-generated pages. Imagine, for example, of a static site that contained demos for Infusion, but also allowed users to submit Github links to cool demos they'd created of Infusion.”

Imagine, too, a Grunt task that causes the Infusion documentation to be republished automatically any time a new supported API is added to the source code, or something like that. There are lots of potential possibilities.

I hope this helps,

Colin