By statistics alone, Wordpress is a winner. According to the stats on Wikipedia, it is a clear favorite amongst the top and new websites worldwide. The sheer volume of options for plugins, themes and customizations are enough to make it worthwhile as a content platform; the admin tools make editing and publishing a breeze.

And yet, yesterday, I ditched Wordpress. This site is now hosted on Github Pages.

So why switch? There are a few reasons. For one, site performance benefits of Pages over Wordpress have been well-documented. Now I don't have to worry about Bluehost suspending my service anymore. Pages is free. There's also my personal distaste for PHP, though it hasn't stopped me from hacking on my pages here and there.

There is, however, a more fundamental reason, illustrated when I ran into a close friend recently. My friend is brilliant and well-regarded in his field (finance). When he remarked on that fact that I had built my own website, my first thought was "Well, not really...", though I said something more like "Thanks!" My friend and most people don't care if a website runs on Wordpress, Django, .Net or C#... but I do. If the general sentiment on Hacker News is any indication, most developers care as well. Many of us got into programming because we saw something that amazed us and we desperately wanted to know how.

To host on Github Pages means for me using git, hand-crafting html and writing markdown in my editor of choice, building with tools written in languages I love, and rolling my own theme built on CSS frameworks I like. It's a better representation of what I do and how I prefer to do it. Using Wordpress has always felt a bit disingenuous. And that's why I made the change.

Discuss on Twitter · Published on Mar 25, 2013

Did you like this post?

Please share it on Twitter and enter your email below to subscribe to my newsletter on GitHub and the web. Thank you!

    Powered By ConvertKit

    More posts

    3 ways Webpack surprises web developers

    When I first started working with Webpack, I was in for a few surprises. I assumed how things should behave, based on my previous experience with the Rails asset pipeline, only to learn through experience how I was wrong.

    Importing images with Webpacker

    Using images bundled by Webpack can get confusing. 'How to reference images from JavaScript? from CSS? from Rails ERB templates? This post will demonstrate.

    Overpacking: A common Webpacker mistake

    A big issue that comes up with Webpacker is "where to put the JavaScript files". This post demonstrates proper use of entry point files, called packs, with Webpacker and Rails and will help developers avoid a common gotcha.

    Logs pexels photo