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 it on Twitter · Published on Mar 25, 2013

Need help with webpack on Rails?

My name is Ross Kaffenberger.

Webpacker now ships by default in Rails 6 but there's no need to stress. I'm putting together a course to help you master webpack on Rails.

I teach full stack web developers about frontend tools and performance, especially at the intersection of JavaScript and Ruby on Rails.

Subscribe to stay in the loop.

    Powered By ConvertKit

    More posts

    The webpack plugin I can't live without

    In this post, we'll take a look at installing and using the webpack-bundle-analyzer, perhaps the most invaluable webpack plugin, to analyze and debug the output of the webpack build in a Rails project configured to use Webpacker.

    Why does Rails 6 include both Webpacker and Sprockets?

    A new Rails 6 application will install both Webpacker and Sprockets by default. Don't they solve the same problem? This article dives into why Sprockets lives on even though webpack has surpassed most of its features and why you might want to choose one over the other.

    How to debug webpack on Rails

    Understanding your Rails webpack configuration and build output can be a little confusing, especially if you're new to either Rails or webpack. This post contains a few tips for debugging your Webpacker setup, some specific to Rails Webpacker, some generally applicable to webpack.

    Logs pexels photo