Hello, Jekyll

Starting today I become part of Jekyll powered website.

What’s Jekyll?

Jekyll is a simple, blog-aware, static site generator. It takes a template directory containing raw text files in various formats, runs it through Markdown (or Textile) and Liquid converters, and spits out a complete, ready-to-publish static website suitable for serving with your favorite web server. Jekyll also happens to be the engine behind GitHub Pages, which means you can use Jekyll to host your project’s page, blog, or website from GitHub’s servers for free.

Why Jekyll?

Tom Preston, Github co-founder, said,

"I was tired of having my blog posts end up in a database off on some remote server. That is backwards. I’ve lost valuable posts that way. I want to author my posts locally in Textile or Markdown. My blog should be easily stylable and customizable any way I please. It should take care of creating a feed for me. And most of all, my site should be stored on GitHub so that I never lose data again."

What I used to for setting up my website: setting up server (usually linux) or buying some shared host, setting up the Content Management System, configuring the templates, etc, backing up and restoring mysql database, setting up web server, and so on, and so on. Before writing anything.

Jekyll is different. There is no database. No awkward theming rule. All are just files inside a folder. We can start write instantly. We can modify files, moving and renaming them, and can instantly see the result via local server. All looks like a normal structure of a website. Later, after all has been settled, we just need to push files to remote git repository (or via ftp or rsync, whatever), to make it publicly available. As simple as that.

I am happy with this start. I really wish you can see me more productive with this environment again. Blogging should be fun, again.

PS: https://github.com/widianto/arifwidianto.com is the git repository for this website. Feel free to check it out to see how my setup for this website.

Join the Conversation

1 Comment

Leave a comment

Your email address will not be published. Required fields are marked *