Help newcomers get started (and be impressed)

[jmatsushita]

Since you brought up marketing I thought maybe I'd share more thoughts hoping there might be some ideas there you might like. :)

I guess when I started reading your slideshow it didn't load the first time around, and then when it finally opened I was a bit... wtf?! is that serious... then I got into it and was chuckling and impressed. But maybe not everyone will stick with it? :) Maybe doing a less fancy landing page (but keeping the fancy slideshow!) would help? Sorry, I'm sure you really love it and I actually think that departing from the shiny/smooth/new fancy bootstrap design trends is great. :)

I'm not very good at writing prose, but it seems that the Readme could be better structured too. I'd suggest as a first easy step to add (maybe before the Built-in Plugin header) for Grunt and Gulp users 2 short(ish) explanation of:

• If I have this in Grunt (Gulp)
• Then that's how it would look like in Sigh
• And maybe finish with a few things you can't do in Grunt (Gulp) and that you can in Sigh

There might be other things to do to make it easier to get started. I could submit a pull request on the Reeadme if you're insterested but I think I need to spend a bit more quality time with Sigh before :)

By the way, why is it called Sigh? Is that the sound you made when you were using other build systems?

[insidewhy]

Great suggestions. The presentation was for a talk at the London node user group, the readme should be the primary documentation and you're right, it could do some work.

Is that the sound you made when you were using other build systems?

Yep :)

[iTob191]

It would probably also help to work on windows compatibility:

• sighjs/sigh-cli#6
• Maybe also allow Sighfile.js (and sighfile.js) as file name because at the moment windows doesn't run the sigh-cli script when executing "sigh" in the command line (if your cwd is the one containing the sigh.js file) and instead tries to execute the sigh.js file (or at least i think it tries to :D).