Usually a website of a single country will be structured as such:
/content/mysite/language-masters
-> /en
-> /es
In the case of a global site you also have country-specific routes that are formatted the same way.
/content/mysite/us
-> /en
-> /es
/content/mysite/ca
-> /en
-> /fr
The sites with "language-masters" as the 3rd part of the path can serve as your "global" website, and you are ideally hiding the "/content/mysite/language-masters" portion of the path via your sling mappings and dispatcher configurations.
To serve the global sites, my general recommendation is to only do a live copy from the global English site (/content/mysite/language-masters/en) to all of the country-specific English sites (/content/mysite/<country>/en) and then use those to individually translate content.
Though it can be tempting to try to save translation costs by having a non-English version of the global site, and inherit Live Copies down to the various countries, in practice this can be very limiting since:
- Languages are often slightly different across countries - i.e. Candian French and France French are not the same.
- If you do this, you now need to author all localization (changes from the global content) in each language.
So my default recommendation for content is:
- Add new content to the global site at /content/mysite/language-masters/en
- Roll out new content down to all country-specific English sites (/content/mysite/<country>/en)
- Where necessary, localize content within each country-specific English site
- Translate the country-specific English sites to the different language sites within each country
That said, this is always nuanced, so let me know if business challenges prevent this from working in your situation.
