Multilingual
Colleagues,
and who solves the problem of multilingual content? taking into account SEO of course and all other ryushechek!
My main postulates are:
')
1) Different languages in different subdomains (en.mainsite.com de.mainsite.com mainsite.com ––> default)
2) Automatic selection of the language to the client during the first visit (selection either from the IP database or from the browser language)
3) CNC language specific
4) All content in a shared DBMS
5) All media (pictures, etc.) live on a separate subdomain media.site.com
6) In the skin, the language binding goes through the language file (loaded into the template) - it is easy to calculate from the name of the subdomain which language to use the file (the cache is already a separate topic, but also implemented)
and who solves the problem of multilingual content? taking into account SEO of course and all other ryushechek!
My main postulates are:
')
1) Different languages in different subdomains (en.mainsite.com de.mainsite.com mainsite.com ––> default)
2) Automatic selection of the language to the client during the first visit (selection either from the IP database or from the browser language)
3) CNC language specific
4) All content in a shared DBMS
5) All media (pictures, etc.) live on a separate subdomain media.site.com
6) In the skin, the language binding goes through the language file (loaded into the template) - it is easy to calculate from the name of the subdomain which language to use the file (the cache is already a separate topic, but also implemented)
Source: https://habr.com/ru/post/59046/
All Articles