Tim Addison

Migrating from Jekyll to Gatsby

After some tinkering with GatsbyJS, I was pretty excited about moving my blog over from Jekyll - great performance, SEO and accessibility out of the box were one reason, and the fact I know far more React/JS than Ruby was another. This post covers my experiences, as well as a few shortcuts that helped make the transition relatively painless.

A little history

When I first started the blog I was fairly committed to getting up and running as fast as possible - spend time writing content, not endlessly tinkering with a site bereft of any content. In some previous attempts to start blogging, I’d get derailed when I started to write my own blog engine. As you can imagine those efforts didn’t amount to a great deal.

Although I was aiming for low-friction I did still impose a few constraints:

  • I should own my content (eliminated blogging on some platforms)
  • The content to be trivially portable (eliminated Wordpress, etc.)
  • Content should be easy to write anywhere (this led me to markdown)
  • Low/zero initial and ongoing cost
  • A template I could live with (desktop + mobile)
  • No ads
  • Fast

Jekyll on GitHub pages was what I settled for, largely influenced by this post from Phil Haack.

Fast forward to today and I’ve been pretty happy with the authoring process. There are a few rough edges, though I blame most of them on my lack of experience with Ruby (rounds down to zero).

The new stack

After building a few other projects with GatsbyJS + Netlify I realized that my current blog workflow needed update. When I ran my blog through Lighthouse I realized that I’d been neglecting visitor experience because I was happy with my authoring experience.


Moving the blog posts to the Gatsby pipeline had a significant impact on all the Lighthouse metrics (higher is better):

Best Practices79%100%

These scores don’t capture the significant impact that Gatsby’s image toolchain can have. In keeping with the ‘low friction’ approach to authoring I had been…a bit lazy with my images, and rarely bothered to compress them or optimize them for the web. Since moving to Gatsby that all comes for free in addition to a bunch of other optimizations - see gatsby-remark-images for more details.

To demonstrate the impact this had, take a look at the impact of running images through the Gatsby pipeline had for the about page (lower is better):

First Contentful Paint1.1s0.8s
Time to Interactive1.8s1.6s
Max Potential Input Delay640ms70ms

It’s easy to forget that not everyone is browsing on a 4G connection from a desktop device. Speed matters, and having that baked in for free was great.


One of the most compelling reasons to migrate was moving to a language/stack I was comfortable coding in. Gatsby sits on top of React/JavaScript - I’m no expert there but I’m infinitely more qualified in JavaScript than Ruby. There was a bit of a learning curve with GraphQL (which I’d never used before Gatsby), though the documentation of both GraphQL and Gatsby are excellent, and if you do make the switch I’d encourage you to read and digest them.

Having a little more experience with frontend development I was comfortable dropping the requirement for an ‘out of the box template’ that I’d be happy with, and I started with nothing more than gatsby new and built from there. I’ve been very impressed with Tailwind CSS and enjoyed building a template from the ground up and finishing it (take that 2013-era Tim!).

Developing with Gatsby is extremely smooth, and I love the fact I can trivially preview a production version of my site locally - I’ll confess with Jekyll and GitHub pages I may have ‘committed until it works’. Again - I’m sure some of this is down to my ineptitude with Ruby, though I will say the Gatsby experience is very straightforward - gatsby build && gatsby serve.


I’ve never had any issues with GitHub pages hosting, though now I’ve seen Netlify I don’t know if I could go back! A couple of fantastic features:

  • Generous free tier (including custom domain + SSL)
  • Deploy previews (open a pull request and Netlify will build a preview for it)
  • One-click setup (I connected to GitHub and Netlify figured out the rest)
  • Server-side redirects (I moved my blog to /blog/ so this was important for me)

If I’m feeling brave I can still push directly to master and know my site will get built and published, so this ticks the low-friction box.

Migrating from Jekyll to GatsbyJS

Building the new site

You can (and I did test) go straight to gatsby-starter-blog. There are a bunch of starters available for a blog (Gatsby’s strong ecosystem is another reason I moved to it), though I ended up doing quite a bit of customization. The main changes from the template were:

  • Add Tailwind CSS and Purge CSS
  • Style the blog posts with Tailwind utility classes
  • Add opengraph share images to each post
  • Add pagination
  • Add an archive page
  • Add a tag page
  • Add a responsive menu

You can see the source (as well as the painful journey of trial and error in the commit history!) on GitHub.

The following posts were incredibly helpful in getting up and running:

Migrating blog posts

The migration was fairly straightforward, and the bulk of the work was moving posts and assets around.

For some reason (lost to me now - I’m sure it felt like a good idea at the time) I had my posts and assets organized like this:

# Post

# Post images

That has always been a minor source of friction in my workflow (why weren’t they colocated!), and the Gatsby way would look more like the following:

# Post

# Post images

I’m sure it would be possible to maintain the current folder structure and stitch the data together in code, though I wanted to move a post and all associated assets around by copying a folder if needed, so I used the following PowerShell to bulk-move everything. Note that I created a new repository, rather than attempting to migrate in-place.

I migrated a few posts ‘by hand’ before running a script, which is what $maxMigrated does.

$sourceLocation = "C:\src\tjaddison.com"
$targetRoot = "C:\src\blog\content\blog"
$posts = Get-ChildItem -Path "$sourceLocation\_posts" -Recurse -File
$maxMigrated = "2019-06-30"

foreach($post in $posts) {
    $date = $post.Name.Substring(0,10)
    if($date -ge $maxMigrated) {
    $year = $date.Substring(0,4)
    $month = $date.Substring(5,2)

    $targetContainer = "$targetRoot\$year\$month"
    $name = $post.Name.Substring(11, $post.Name.Length - 14).ToLower() # remove .md
    $blogFolder = "$targetContainer\$name"

    # Move the blog post
    New-Item -ItemType Directory -Path $blogFolder
    Move-Item -Path $post.FullName -Destination "$blogFolder\index.md"

    # Find any assets (images, source code, etc.)
    $imagePath = "$sourceLocation\assets\$year\$date"
    if(Test-Path $imagePath) {
        Get-ChildItem -Path $imagePath -Recurse -Force | Copy-Item -Destination $blogFolder

Because the images had been moved the references in the markdown posts needed to be updated - in hindsight it is a much saner system to have the images colocated and all references relative. I used the following regex in VSCode to bulk-replace all image references, as well as the shareimg frontmatter.

# Images

# shareimage
(shareimage: http.*/)(.*)
shareimage: "./$2"

What’s next?

One outstanding feature I’ve not yet solved is comments. A few times over the years I toyed with adding Disqus but the level of stuff it injects into the site (ads, trackers, etc.) is frankly obnoxious. I did use Staticman for a while but found that the spam protection just wasn’t strong enough and I experienced a few issues around availability. Tania Rascia has a great post to get a system up and running with Node.js/Express/PostgreSQL - this is a little beyond my target complexity, so I’m already toying the idea of rolling my own system atop Cloud Firestore or Netlify Forms.

I’m still chasing down a few areas where the site is not as accessible as I’d like, and I’ve got some ideas on what an improved home page might look like…but mostly I’m pretty happy with how it looks and excited to focus on writing post again rather than migrating them.

Let me know if you have any comments or suggestions (by email for now, there is no comment system!)