Jekyll work flow

As you might be aware I’m running this blog using an awesome software ( I’m not sure whether I can call that ) called Jekyll.

Jekyll is a simple, blog aware, static site generator. It takes a template directory (representing the raw form of a website), runs it through Textile or Markdown and Liquid converters, and spits out a complete, static website suitable for serving with Apache or your favorite web server.

But, it is not this feature set that provides Jekyll’s awesomeness - but it’s set of users. The jekyll user base primarily consists of programming experts and web programmers. Case in hand, Jekyll was writtern by one mojimbo aka Tom preston werner who is also one among the founders of the revolutionary Github. It’s quite a mix with entreupreneurs, students and programmers in the mix.

End result - All of them want to use software in their own way, in their own style resulting in loads and loads of forks and useful plugins.

So, what has this got to do with my workflow. I just wanted to point out a couple of useful plugins I found


is a script is intended to automate the process of creating and editing Jekyll blog posts from within vim. It works quite well and does what it advertises to do - create new posts, commit to a Git repo and deploy it.

Jekyll Vim

It now forms an integral part of my blogging joy.


is another ruby bin o easily send a jekyll powered blog to your host through FTP. Unlike most of the users of Jekyll, I don’t trust my content to GitHub preferring to use my own FTP server instead. Although archaic, this is the method I’m most comfortable with.

EDIT: I’m still trying to get this work perfectly

Markdown Syntax for Vim

This is kind of a trivial thing, but that is what which separates the good from the great, right ? Simple, workable Markdown Syntax file.

So, what is my workflow

  1. Fire up Vim
  2. Use Jekyll vim to create a new post / edit an old one
  3. Check the output by running jekyll --server
  4. Apply the finishing touches and make everything pixel perfect
  5. Hopefully, deploy my blog using glynn

And there you go, the workflow of a g33k