Adrien Harnay

In my previous post, I explained how I migrated my blog to Next.js. Today, I wanted to explore Next.js API Routes and how they can help us build a back-end for our front-end application.

Gatsby and Next.js are two tools that get praised a lot for personal blogs and static websites, and each year there is more and more stars and contributions on Github. I recently migrated my website from Gatsby to Next.js, and I will list the differences I have noticed.

When working with open source packages, you may find a bug that has not yet been fixed, or the PR has not been merged yet. So what are your options... Fork the package? Depend on a git commit and build manually? There is a simpler solution!

If you have ever worked with Open Source projects, and in particular in the React and React Native ecosystems, you may already have found the need to use `sed` to manually patch a package. Unfortunately, the syntax on MacOS and Linux differ.

When working on responsive websites, you will often want to adapt to the user's screen width so your content could be responsive. SASS mixins allow you to do it in a readable and maintanable way.

At my daily job at brigad.co, I have been using React, React-Router and Webpack for quite some time. When we needed to improve our SEO, so we could rank higher in search engines, Server Side Rendering came as an obvious choice. [...] So I went and implemented my own solution.

Do you need to build a MVP for your start-up? Or a new feature for your product but your teams don't have the time? Do you need to implement a new solution and want someone with experience to do it and/or teach your team? Reach out to me!