From Wordpress to Jekyll
In my very first blog post, I rambled a little about choosing between a static site generator and a blogging CMS. I said how it doesn’t matter whatever tool I decided to use, and went with Wordpress in the end. Today, I’ve fully migrated my humble little blog to Jekyll.
So why switch?
- My overarching principles for designing and building things is speed and simplicity. It affects my choice of tools as well.
- Worrying about outdated Wordpress plugins is inane.
- Having a database for a simple blog is overkill. Besides, storing blog posts in a database may not be such a good idea.
- As a web developer, I live in a text editor and the command line.
- I ♥ Sublime Text.
- I tried to make my life easier by using TinyMCE (yet another plugin) and custom styles to append classes. I quickly realized that it made no sense.
- Markdown is fast.
- I got up and running with Jekyll in 10 seconds. Jekyll new site, Jekyll serve. No more messing with Vagrant! (I still use it for other projects though)
- Site deployment is so much simpler.
- Sick and tired of jumping through hoops just to include files. wp_register_script(), wp_enqueue_script(), maybe try a plug-WHAT?
I had a little bit of anxiety when I thought about wiping my Wordpress installation off the server. So glad I did. Writing is fun again; I’m almost done with my next post.
Of course, not everything is nice and rosy with the switch. I was absolutely spoilt by Wordpress and Yoast for Taxonomy and SEO management. If you’re thinking of switching over to a static blog as well, consider these resources for a smoother transition:
- Simple Jekyll search - Alex Pearce
- Custom Meta Info with Jekyll - Dave McNally
- Critical-path CSS - Addy Osmani