Let's keep in mind that locales are comprised of two parts: country code and language code. A Spanish article written by a person from Colombia is not going to be exactly the same as if that person were from Spain could write and viceversa. French in Canada is not exactly the same French for France or Senegal. So we might want to take countries into account as well.
Not sure if we should differentiate those or not, maybe not from the start, but we should take into account that the full locale is de-AT, de-CH, de-DE, not just de and some products simply read what the browser locale and "route" the user to the strings translated in the specific locale.
A possibility would be to have it-it from the start in the URL and serve the same Italian to both it-IT and it-CH so that when we'll have a reason to translate to it-CH that won't change.
I guess this decision has to be made for the caching keys as well ahead of time
I think if country and sub-region is something we want to support, it's common to do something like /us/en (Ikea is one example). We definitely should make a call on this upfront.
It seems a lot of the "large" companies go as far as changing the domain itself (i.e. adidas.de, airbnb.de, airbnb.com.co). That approach has advantages, including SEO and code implementation. That will be much tougher for Forem since we're talking about infinite communities and domains to manage.
For further actions, you may consider blocking this person and/or reporting abuse
On additional aspect, related to subdirs.
Let's keep in mind that locales are comprised of two parts: country code and language code. A Spanish article written by a person from Colombia is not going to be exactly the same as if that person were from Spain could write and viceversa. French in Canada is not exactly the same French for France or Senegal. So we might want to take countries into account as well.
Not sure if we should differentiate those or not, maybe not from the start, but we should take into account that the full locale is
de-AT,de-CH,de-DE, not justdeand some products simply read what the browser locale and "route" the user to the strings translated in the specific locale.A possibility would be to have
it-itfrom the start in the URL and serve the same Italian to bothit-ITandit-CHso that when we'll have a reason to translate toit-CHthat won't change.I guess this decision has to be made for the caching keys as well ahead of time
I think if country and sub-region is something we want to support, it's common to do something like
/us/en(Ikea is one example). We definitely should make a call on this upfront.It seems a lot of the "large" companies go as far as changing the domain itself (i.e.
adidas.de,airbnb.de,airbnb.com.co). That approach has advantages, including SEO and code implementation. That will be much tougher for Forem since we're talking about infinite communities and domains to manage.