I'm looking for some advise on how to handle/structure a multilingual site with shared content.
What I tend to do when creating multilingual websites is to have a website for each language, i.e.: mysite.dk, mysite.co.uk, mysite.com etc.
However, in this particular case I need to have a 'folder'/repository which acts like a small 'database' of shared content that can be used in any of the sites. The problem here is, that the content of these nodes will only be in one language and thus will appear on i.e. danish in the english website.
The best solution I can think of at the moment is to have a tab on these shared nodes for each language supported. I.e. a tab for danish content,a tab for english content and so on.
Just wanted to hear if anyone has got a better solution to this since my idea is quite restrictive.
I'm not sure I understand fully, so the 'shared content' is only in one language but's it's to be displayed in each language site regardless?
If so I would just create an extra site / node named 'Shared Content' and use a content picker or XSLT / Razor to pull out what I needed in each multi-lingual site.
Last week on the Dutch Umbraco Festival 2012 I saw a session given by Niels Kühmel on creating a one on one multilingual website with Umbraco. It's pretty much the structure you describe, using tabs for each language.
I'd like to show you the structure I'm planning to use. I'm not really one for 1-1 multilingual sites, don't ask me why though ;-) I just find it restrictive, I guess.
Anyway, here's the structure I'm aiming for:
So basically I have a site for each language and then all the shared content which can be used (with a multinode picker) I've been thinking a lot about this structure and the only drawback I am able to find is that constantly have to check which site the client is on when rendering the shared content - maybe by having a dropdown list with the values "dk,us,uk,ge" to check against. This would cause all code to crawl to the root node every page load which doesn't seem ideal at all.
Having the shared content in each of the sites is not an option since there will be, in addition to Slideshows and Modules, a recipe-"database"
Looking for pros/cons and maybe alternative ways of doing it like this. Maybe a smarter and more effecient way to determine language tab to render from the shared content?
Multilingual site with shared content
Hi all,
I'm looking for some advise on how to handle/structure a multilingual site with shared content.
What I tend to do when creating multilingual websites is to have a website for each language, i.e.: mysite.dk, mysite.co.uk, mysite.com etc.
However, in this particular case I need to have a 'folder'/repository which acts like a small 'database' of shared content that can be used in any of the sites. The problem here is, that the content of these nodes will only be in one language and thus will appear on i.e. danish in the english website.
The best solution I can think of at the moment is to have a tab on these shared nodes for each language supported. I.e. a tab for danish content,a tab for english content and so on.
Just wanted to hear if anyone has got a better solution to this since my idea is quite restrictive.
Thanks in advance.
All the best,
Bo
Hey Bo,
I'm not sure I understand fully, so the 'shared content' is only in one language but's it's to be displayed in each language site regardless?
If so I would just create an extra site / node named 'Shared Content' and use a content picker or XSLT / Razor to pull out what I needed in each multi-lingual site.
Rich
Hi Bo,
Last week on the Dutch Umbraco Festival 2012 I saw a session given by Niels Kühmel on creating a one on one multilingual website with Umbraco. It's pretty much the structure you describe, using tabs for each language.
You can checkout his session here:
http://duf.sharetu.be/video/40788814
greetings,
Anthony
Hi Rich and Anthony,
Thanks a lot for your inputs :-)
I'd like to show you the structure I'm planning to use. I'm not really one for 1-1 multilingual sites, don't ask me why though ;-) I just find it restrictive, I guess.
Anyway, here's the structure I'm aiming for:
So basically I have a site for each language and then all the shared content which can be used (with a multinode picker) I've been thinking a lot about this structure and the only drawback I am able to find is that constantly have to check which site the client is on when rendering the shared content - maybe by having a dropdown list with the values "dk,us,uk,ge" to check against. This would cause all code to crawl to the root node every page load which doesn't seem ideal at all.
Having the shared content in each of the sites is not an option since there will be, in addition to Slideshows and Modules, a recipe-"database"
Looking for pros/cons and maybe alternative ways of doing it like this. Maybe a smarter and more effecient way to determine language tab to render from the shared content?
Thanks again.
All the best,
Bo
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.