Localization with NextJS and Github Pages

[skjelmo]

Goal:

• Serve content on kodeworks.no in Norwegian and English

Preferred solution:

• Sub-path routing (/en/..) without sub-path for default locale (norwegian) (/..)

Problem description:

• NextJS built-in Internationalized routing is not supported with static html exports required for hosting with github pages.

Chosen solution at the time of writing

• Focus on the Norwegian content only
• When english is required, add duplicate page components for the english URLs, and investigate how to minimize duplication e.g. by sharing page components that accepts language as input using an i18n-package for translation

Possible solutions

Create a page component for each language

• Duplicate code for all pages

hosting with node.js server

Deploying with CLI should support multiple users without exceeding free tier. However, the pricing plan limits the number of users who have access to the hosting dashboard.

Vercel

• Deploy with CLI.
• Deploy with Github actions

Cons:

• Only one user has access to the hosting dashboard vercel.com

Layer0

Netlify

Sub-path routing for all locales

• Example with react-i18next
• A solution using Sanity CMS will most probably also create sub-path for default locale, introduce complexity and increase cost more than three users need access.