My journey building my personal webpage with NextJS
Most of the time I spend in front of my laptop is working on the hidden side of DevOps and BackEnd developments. However, some times, I get over the other side to not forget my little knowledge about the frontend world. This time, I decided to rebuild my old-fashioned personal webpage from scratch using the NextJS framework.
Next.js is a React framework to create a zero-configuration, SSR (Server-side rendering) project.
I was looking for solutions to increase the SEO/SEM trying to figure out an alternative to get over an SSR application with React when I ran across Next.js. Rendering the webpage from the server instead of the client is essential to get over a good SEO/SEM.
Furthermore, I feel comfortable using React in the frontend and despite the fact I love learning new frameworks and technologies; in this case, I didn’t want to make life difficult and have my new webpage finished as soon as possible.
As a DevOps engineer, the easier is the CI/CD implementation, the merrier. With Next.js, you don’t have to worry about that because the Next.js’ team also created an all-in-one platform named Vercel. Only defining your GIT provider within your Vercel’s configuration, it’ll delivery the latest changes in a volatile instance with any commit you push.
On the whole, I came round that Next.js is, in my opinion, the best framework to build your React application in the server-side. I will create new posts explaining the issues I have been finding in this journey such as Material-UI adaptation, Markdown conversions, dynamic metadata, dynamic paths, etc. Do you know any alternative better than Next.js?
