Next.js migration

[gorzelinski]

Is your feature request related to a problem? Please describe.

Although Gatsby is great for building things fast with plugins, it's a double-edged sword. The official theme for internationalization is no longer maintained. The last change is from two years ago. Because many plugins rely on this one, it blocks the ability to update them.

Describe the solution you'd like

I want to migrate the whole project to Next.js. It is the most popular static site generator on the market right now. But hype shouldn't be a decisive factor in choosing a tool. The tool should be proper for the job. However, Next.js power many blogs, and they work nicely. Migrating a website is also an opportunity to learn new stuff. Migration may be tricky. There are many tasks to copy all functionality:

• Update packages and dependencies.
• Delete Gatsby-specific scripts.
• Add Next-specific scripts.
• Change folder structure.
• Change routing.
• Copy CSS-in-JS styling.
• Update Link component.
• Change data fetching strategy.
• Update Image component.
• Update SEO component.
• Deploy on Vercel.

Describe alternatives you've considered

There are unofficial plugins for i18n. There is also an option to build everything by hand from scratch. But, relying on such plugins is risky, and reinventing the wheel is not the best idea.

Additional context

Helpful migration guides:

• https://www.hatimeria.com/blog/article/how-to-migrate-from-gatsby-to-next-js
• https://marcoheine.com/blog/migrating-from-gatsby-to-nextjs
• https://www.dandoescode.com/blog/migrating-from-gatsby-to-nextjs
• https://vercel.com/guides/migrate-to-vercel-from-netlify
• https://jeffjadulco.com/blog/migration-next
• https://dev.to/dionarodrigues/migrating-my-site-from-gatsby-to-nextjs-13-the-pros-and-cons-358n
• https://blog.maximeheckel.com/posts/migrating-to-nextjs/

The issue that describes the problem with I18n - #36.
The TypeScript migration can be a follow-up - #37.

[gorzelinski]

Closed by: #55