Blog: Migrating Site to Next.js
This month, I'm beginning the process of migrating my personal site toward using Next.js.
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 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
- 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
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.
I have a passion and successful track-record for creating usable, online, experiences with a focus on and deep appreciation for web standards, modularity, education, accessibility, and inclusion. I build and lead happy, productive and empathetic cross-functional teams within a continuous learning culture. I am a father, speaker, advisor, life-long learner, community builder, advocate and a Human Being. Learn more.