Saumya

First question to answer is why I moved to a static page solution?, there are a lot of answers to this. Here is a nice writeup by David Tucker. The Need for a Static Site Generator.
Now, since we know a static page site is the need of the time, the technology choice is important too. Obviously the first thing, that comes to mind is Jekyll, yeah, its simple and just works. Being in MAC, its even tempting to use Jekyll, as Ruby comes installed with the OS. Further more Jekyll support is in-built with GitHub Pages. It could have been as simple as that.
I choose Javascript as the language of choice, since its exciting now, what we could do with it, so this blog would be one of my playgrounds for the work I do. I have already getting more and more familiar with Jade templating engine and nodeJS workflows, wintersmith is such a nice engine which works on nodeJS. Just the matter of time, as how far Javascript has come!

Happy Coding

After a week of searching, studying and re-searching things, finally landed up with this. Well, there is not much to wintersmith, it 10 mins job at max if someone has a little experience in NodeJS.The main delay for me was to trying to produce a static site out of my old blog, which was running in WordPress eninge.

Cheers.

Do you notice ?! Now this blog is served from Github itself. The publishing was never excicting as this.

How it works? Git commit and the post is out there.