nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Multi language DCR/Site considerations

Srinivasa Talla

If I have a DCT for contact us, can I save DCRs in different languages? or create individual DCT for each language? or need to mention the language at site level?

I would like to load particular language DCR based on user selection. Is it possible or any issues with languages feature?

Find more posts tagged with

Comments

nipper

There is OOTB functionality for LSDS to choose the correct language. Read the SP developers guide.

In a nutshell, if you are set for es_mx, and have a component referencing contact-us.xml, it will first look for contact-us_es_mx.xml, then contact-us_es.xml and finally contact-us.xml

Srinivasa Talla

Thanks for the reply. Here it has 2 parts

1. I can save the DCR in different languages for same contact us DCT. - Is that true?

2. Choosing respective language DCR, sure OOTB will help with that. Thanks for the tip.

nipper

Different names implies different DCRs.

You can certainly write XSL that will do something similar if you want and read it out of the same DCR.

Srinivasa Talla

Cool, thanks. I appreciate your help. So it is possible. Then

what is the advantage of maintaing different sites(like /en/,/fr/,...) Vs just maintain different DCRs?

If I am able to handle the language feature through DCRs, I don't need to maintain different sites, right?

Example: Assume I have to display 5 pages for a website and in 3 languages.

Option 1 : Maintain 3 sites(or even folders) and keep 5 pages in each site. Each site represent a language.

Option 2 : Maintain 1 site and keep different DCRs for each language. We may have different folders for images.

2A. But pages are just 5. Components handling the DCRs display with page parameters(contactus.page?ln=1).

2B. Pages could be 5 x 3 = 15. contactus_en.page, contactus_fr.page, contactus_ch.page. Which is best 2A or 2B or something else?

Either 2A or 2B, there should not be any issue with SEO. Page title, meta description and page content will be in that particular language. Any other issues?

Is Option 2 not simple for end user or maintanance person? or any other issues? Any issues if we are adding 4th language?

How this whole design will change if we have 50% english pages? That means, only 50% pages will have the language option. Total 100 pages. In that 50 are alwasys english, remining 50 are language combination. Still 2A is best?

testThaiLanguage_iHub31.pdf

Ashish_Sangal

Hi Guys,

Can anyone please through some light on the above scenario mentioned by raot.

Manumagician

As per previous comment, you are using Sitepublisher along with TeamSite.

Maintaining a different folders for locales under the sites folder is actually creating different sites namely en/fr/ch and so on, this helps not only to authors to manage page easily but also help search engines to track the pages for different locales and improves search at organic search level

You can create master locale and child locales in configuration setting of the branch and accordingly different locales DCR folders will be created. Using this helps maintain a cleaner workarea and maintainence in future is not a challenge.

I would suggest to go for option A.

Rick Poulin

Option 2B is just a much uglier version of Option 1, so there's no value in that.

You could go with option 2A if *all* of your content is in DCRs, at which point I would question the value of using SitePub at all.

The value of splitting up your sites by locale is that it gives you the most flexibility. You can use regular components for most of the content and then use DCR-backed functionality where structured and/or dynamic content makes sense for your use cases.

testThaiLanguage.pdf