Now my client is asking for a structure like this:
Israel - he-IL - ar-LE - en-US
Japan - ja-JP - en-US
His argumentation for this structure is that the content will be different for Israel and Japan, and for each country the content will be available in different languages.
I'm wondering if this content structure that my client suggest is:
a) feasible: can multilingual content be structured like this? What about, for instance, with the two en-US nodes?
b) Can't the feature of having different content for Israël and Japan be realised with the content structure I set up?
Is the content on the en-US site supposed to be different when visiting it from Israel rather than from Japan and vice versa? Or is it indeed the same site he wants to have two different places in the structure?
The way I understand the above is that you have 4 different sites (your approach) and that the content on each of these sites differ dependent on, which language you visit, right?
If that is correctly understood then I don't think the suggestion by your client makes much sense - however I'm looking forward to hear more from you :)
Thanks for your advice. The way I understood it is that the content on the en-US site will be different when visiting from Israel or Japan.
Yes, in my content structure there are four different language sites, where there I did a copy of the en-US node with the option 'relate copy to original' selected.
Because that's the point of multilingual website right, To have different language versions of the same content :)
But now it seems my customer wants two websites (Israel - Japan), with different language options for each website (sigh).
So now I'm assessing if my customers supposed structure is feasible, and if I can redesign my current structure in the structure that my client wants.
Ok, so is the domain different from Israel and Japan? Or is it website.com for both?
But then I guess your clients structure could make some sense. For instance if there are going to be a lot of editors and the ones editing the japanese versions should only see those two websites in the tree then it's easier to setup in the user section for instance.
They won't have a different domain. As far as I know, all websites will have the co.il domain.
Yes, I'm starting to see the sense of it too, I'm only wondering about the rework I'll have to do to change the structure I already have into the structure my client wants, with breaking anything :)
Currently I redesigned the multilanguage content structure to the whishes of my client:
The hostname of the 'Israel' node is: energypartner.co.il
The hostname of the 'Japan' node is: energypartner.co.jp
What I need to do now, is to configure a permanent redirect, so when a visitor visits www.energypartner.co.il he gets automatically redirected to the Hebrew homepage: www.energypartner.co.il/he
and when a visitor visits the Japanes website: www.energypartner.co.jp he get automatically redirected to the Japanes homepage: www.energypartner.co.jp/ja
The way I solved this, is by creating a property 'Internal Redirect ID' (alias 'umbracoInternalRedirectId') of type Content Picker. Then I can set for every Country node (Israel, Japan) a permanent redirect to a default homepage:
This way I implemented the customers specification for having two website nodes (Israel, Japan) with different language versions for every website.
Hope this can help some other Umbracians implementing their multilanguage site structure in Umbraco
need some advice about a multilanguage folder structure
Hi,
For a multilingual website, I create this structure in the Content Tree:
- en-US (www.website.com/en)
- he-IL (www.website.com/he)
- ar-LE (www.website.com/ar)
- ja-JP (www.website.com/ja)
Now my client is asking for a structure like this:
Israel
- he-IL
- ar-LE
- en-US
Japan
- ja-JP
- en-US
His argumentation for this structure is that the content will be different for Israel and Japan, and for each country the content will be available in different languages.
I'm wondering if this content structure that my client suggest is:
a) feasible: can multilingual content be structured like this? What about, for instance, with the two en-US nodes?
b) Can't the feature of having different content for Israël and Japan be realised with the content structure I set up?
Thanks for your advise,
Anthony
Hi Anthony
Is the content on the en-US site supposed to be different when visiting it from Israel rather than from Japan and vice versa? Or is it indeed the same site he wants to have two different places in the structure?
The way I understand the above is that you have 4 different sites (your approach) and that the content on each of these sites differ dependent on, which language you visit, right?
If that is correctly understood then I don't think the suggestion by your client makes much sense - however I'm looking forward to hear more from you :)
/Jan
Hi Jan,
Thanks for your advice. The way I understood it is that the content on the en-US site will be different when visiting from Israel or Japan.
Yes, in my content structure there are four different language sites, where there I did a copy of the en-US node with the option 'relate copy to original' selected.
Because that's the point of multilingual website right, To have different language versions of the same content :)
But now it seems my customer wants two websites (Israel - Japan), with different language options for each website (sigh).
So now I'm assessing if my customers supposed structure is feasible, and if I can redesign my current structure in the structure that my client wants.
greetings,
Anthony
Hi Anthony
Ok, so is the domain different from Israel and Japan? Or is it website.com for both?
But then I guess your clients structure could make some sense. For instance if there are going to be a lot of editors and the ones editing the japanese versions should only see those two websites in the tree then it's easier to setup in the user section for instance.
/Jan
Hi Jan,
They won't have a different domain. As far as I know, all websites will have the co.il domain.
Yes, I'm starting to see the sense of it too, I'm only wondering about the rework I'll have to do to change the structure I already have into the structure my client wants, with breaking anything :)
Thanks for your advice,
Anthony
Hi,
Currently I redesigned the multilanguage content structure to the whishes of my client:
The hostname of the 'Israel' node is: energypartner.co.il
The hostname of the 'Japan' node is: energypartner.co.jp
What I need to do now, is to configure a permanent redirect, so when a visitor visits www.energypartner.co.il he gets automatically redirected to the Hebrew homepage: www.energypartner.co.il/he
and when a visitor visits the Japanes website: www.energypartner.co.jp he get automatically redirected to the Japanes homepage: www.energypartner.co.jp/ja
The way I solved this, is by creating a property 'Internal Redirect ID' (alias 'umbracoInternalRedirectId') of type Content Picker. Then I can set for every Country node (Israel, Japan) a permanent redirect to a default homepage:
This way I implemented the customers specification for having two website nodes (Israel, Japan) with different language versions for every website.
Hope this can help some other Umbracians implementing their multilanguage site structure in Umbraco
Greetings,
Anthony
is working on a reply...