Beyond the Usual, Passive DEI Efforts in Tech

Blog: Migrating Site to Next.js

Manny Becerra as a child

June 2018

This month, I'm beginning the process of migrating my personal site toward using Next.js, which is an open-source React front-end framework I touched on a couple of years ago. I've been using Next.js for projects since then, it's now time to leverage it for my own site!

We want to empower the individual within the company, we want to empower the small team within a company. So that they don't have to worry about all this technology for scale and performance. — Guillermo Rauch

I'm currently using React alongside SASS to build out my site's UI/X, however, with this migration toward Next.js, I'll be able to continue to build out great user interfaces with React and SASS while also taking advantage of the following:

  • Easily migrate my blog posts and write new ones in both markdown and pull-in from a third-party content source (e.g. WordPress API) thanks to MDX
  • Leverage server-side rendering (SSR) for not just adding SEO metadata but leveraging SEO best practices for JavaScript / JAM stack applications
  • Service Workers that can cache all pages/views, and blog posts for offline reading
  • Optimize images on-demand, especially, when you don't have time to optimize using Photoshop before deploying, and, of course,
  • Easily deploy with Zeit's Now platform

Here to stay

Since Next.js was first open-sourced in 2016, it's seen a steady trajectory of growth, support and reliability; it's clearly not going anywhere, and it's a forerunner in the JAM stack sphere. I'm a fan.

Visit the Next.js website to learn more and how to get started with using it too!


Manny Becerra as a child

I operate from a place of compassion, possibility and imagination. My work and efforts share a common goal: create a better, sustainable and equitable world by building inclusive communities, products & experiences.