Stage 1: add localisation with Next-intl library (built on top of i18n)
Handle locale in middleware (based on automatic detection / user preference)
Fetch localised texts from corresponding json files
Switch to next-intl dynamic text elements everywhere
Also think of the most performant way to detect the current property (e.g. "tdf" or "moos" etc.)
Stage 2: store all localised texts in a database
Ideally we will need to have pages statically generated where possible. This in turn will require using getStaticProps and seriously changing the way we currently fetch data from backend.
Additionally we will need to trigger new build with every database update. An alternative route is to use Incremental Static Regeneration (ISR). But this requires a bit of digging.
Stage 1: add localisation with Next-intl library (built on top of i18n)
Stage 2: store all localised texts in a database
Should also fix #381