on Next JS

I am in the midst of changing my blog’s infrastructure, so I wanted to write up the original infrastructure I used for my blog.

Before I talk about the infrastructure, let’s go back to my reasons for creating a blog:

  • At the time of writing this blog, I lead Product for AMP, so I wanted to eat my own dogfood. Specially, I wanted to test how AMP worked in a framework.
  • I wanted to start being more creative, I had no idea what I wanted to write about, all I knew was that I wanted to write.

So let’s dive into the old infrastructure of the blog:

  • AMP: I wanted to publish AMP pages to make sure that I didn’t have unnecessary JavaScript
  • Next.JS: My team works closely on getting the AMP integration in Next to work and I didn’t know much React syntax so this seemed like a cool new way to kill two birds with one stone.
  • Markdown: I didn’t want to write too much code or mess with too much stuff every time I wanted to publish a blogpost, so converting Markdown to HTML made sense.
  • GitHub: Needed to put the source code somewhere 😛

And that’s that the old infrastructure powering this blog. I am going to be switching to WordPress for reasons… Stay tuned for why I am making that switch. COMING SOON!