Why I chose Gatsby + Netlify when upgrading my Blog's tech stack

September 04, 2018

Writing content, making site design changes, and deploying new site versions should be fast and simple. Otherwise, I’m wasting unneccessary time and energy.

My old website was the first site I ever created, and therefore not easy to create content with.

I finally revamped my site with a modern tech stack that makes it much easier for me to publish content for.


I went with Gatsby instead of Phenomic or NextJS due to its:

  • Ease of getting started
  • Simplicity for my needs as a blog
  • Large community
  • GraphQL support

I went with Netlify due to its:

  • Ease of getting started and deploying via GitHub
  • It’s cost (free)
  • Supports lambda functions

My needs were:

  • Write everything in Markdown
  • Build everything with React
  • Deploy changes quickly & easiliy

Gatsby, Phenomic or NextJS?

I tried all three of these frameworks when starting out.

Note: these are just my experiences and initial thoughts, not in-depth comparisons comparing the merits of each.


I first went with Phenomic because I valued that it was a younger project, and therefore had more opportunities for me to contribute to its source code. Getting started with Phenomic was okay, but the documentation wasn’t as easy to follow as it could/should have been. I later put less interest in open source contribution-potential as a decision-making factor, as I figured I’d prefer to spend free time on other projects.

I knew NextJS and Gatsby were stronger alternatives with larger communities, so I moved onto NextJS.


NextJS seemed cool to me because I’m interested in developing server-side apps, and NextJS is currently the main contender in the SSR space.

However, for my blogging needs, I didn’t find a quick and easy go-to repo to clone that had clean Markdown support. It was a lot of emphasis on markdown-in-js when what I wanted was plain and simple Markdown parsing.

The team was also deprecating the existing markdown plugin in favor of a better one (IIRC to better support my use case of plain Markdown), however, this was all too complicated for me to deal with.

I realized that while NextJS was great for SSR and that I wanted to become more familiar with it, what I really needed was something more basic that was best for blogging and that would get me going super fast.

Winner: Gatsby

Gatsby’s docs are great. They’re super simple, detailed, and well organized. They encourage you to download starter projects from which there are a large variety.

I went with this one which was a blog starter. I cloned it, and just hacked away.

Gatsby has been the easiest to work with and the most developer friendly IMO. I think that’s because Gatsby’s focus is for making static wesbsites like what I wanted. While NextJS might be better for full scale apps, Gatsby was a simpler and easier framework for me and my needs.

Next steps

There are lots of things I need to improve for this blog. I spent a weekend’s worth of time working on this, and my intent was to get a minimum V1 set up.

Moving forward there are needs, by priority:

  • SEO optimization
  • Analytics
  • Progressive web app features / better mobile support
  • Design improvements (can be related to previous point)
  • Social Media sharing
  • Categories
  • More blog metadata
  • A/B testing
  • Better image support, thumbnails, etc
  • Tooling to scaffold blog posts easier (automatically writing out the ISO date)
  • Code clean up

Patrick El-Hage

I'm Patrick El-Hage and I live and work in San Francisco. I'm also on Twitter.