Add "Website Language" to "Website" type definitions
Introduce new assoc type "Translation" (Entity), with "Website Language" as a child topic
Add server-side logic:
Each webpage requested, with "Translation" associations, gets displayed with a dropdown menu / simple menu in the footer rendering a human readable "Label" for each existing "Website Language" tag associated with a "Webpage". Clicking that translation label, will request the visitor the associated "Webpage" (and therefore may switch Websites implicitly)
Each top level html element of a webpage inherits the "Website Language" value set from its associated Website topic (e.g. html lang="en" is added as an attribute.
Maybe, at a later stage, support for "Content negotiation" will be added server-side:
Each request to a webpage/website is parsed for a language preference through inspecting the values in the Accept-Language HTTP header sent by the visitors browser.
The main idea to implement mulit-linguality is now like this:
Extensions to the Application Model:
Add server-side logic:
html
element of a webpage inherits the "Website Language" value set from its associated Website topic (e.g.html lang="en"
is added as an attribute.Maybe, at a later stage, support for "Content negotiation" will be added server-side:
Accept-Language
HTTP header sent by the visitors browser.