The post asks how to create a website that supports two languages and how the CMS content will be translated. Community members suggest that the CMS should store the content, and the dynamic pages can fetch the appropriate language and slug based on the URL. There is a discussion about detecting the user's browser locale and automatically setting the language, with some community members suggesting using the "Accept-Language" header or a separate issue to investigate this further. However, there is no explicitly marked answer in the comments.
The CMS is responsible for storing the content so up to you how its translated. Then in your dynamic page you could do /:lang/:slug and fetch the proper lang and slug based on whats in the URL
THX John ! Is there any way to get the actual "Browser locale" via a kind of "on load" event into a globel variable ? e.g. If the site is loaded from an location in Sweden "se" I'll like to set it to /:se/slug ?
Hmmh , I'm not sure what you mean with "... we should do when working on the Slot task?" But I guess it's helpful/necessary to know initially which locale is current using opens the site to be prepared for setting the /:lang... path dynamically , or ?
this is something to consider separately, these things need to work server-side or allternatively would have to load the site in one language then on the client with js do the detection based on anything else and redirect
