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; } } }

Localizing LiveSite Navigation?

iw_bubbles

Does anyone have experience building a LiveSite site that is localized? We are wondering what the best practice is around localizing the navigation. We would like to avoid creating multiple sites (1 per locale) or using segments. Basically we are looking for a parametric approach that allows pages to be loaded something like detailpage.page?localeID=2.

What approach can we take so that sitePublisher driven navigation is locale aware? Any ideas are greatly appreciated.

Thanks,

Paul

Find more posts tagged with

Comments

chandrachv

As far as i know Sitepublisher cannot filter Locale based components.
I had two approaches which i use in my prj.
One Way is to create Folder structure and create components and Templates in the folder Structure, which is pretty similar to the branching in Teamsite

Like
--Main
--en
--us

the other way is using Targeting engine from the Livesite

I dunno about the second one as we dont have any targeting engine.

but we kind of followed the first approach after consulting with the interwoven guys.

iw_bubbles

Thanks for the reply chandrachv. So in your case you had a deferent .page file for each locale?

chandrachv

Yes i do have different .pages

In My case most of my components are served by dcrs which are locale based, I'm still in the Process of Learning how it works at runtime.

May be i will get back to you later with the standardized Locale based implementation of SitePublisher.

thanks
chand..

tec_iwov

yes you can use DCR to localize data. this is described in the LS documentation

iw_bubbles

Yeah I saw the DCR method in the documentation. That doesn't really help in this case.

Some of our pages need to be smart enough to load data into components from the database. The components on the page have to be locale aware and load the content accordingly.

We are thinking that we can localize the navigation in a similar fashion. Such that the localeID is stored in the User Session object and the navigation component is smart enough to build the links accordingly. Basically we'll need to update the OOTB navigation component so that it can handle locales.

Has anyone done something similar?

jaalex

I know it's resurrecting a very old post, but assuming you've found a solution to this, can you please share how localization was achieved ?

errorExcel.jpg

vpatel

I know it's resurrecting a very old post, but assuming you've found a solution to this, can you please share how localization was achieved ?

This is a very broad architectural question. I doubt you'll be able to get a complete answer to such topics on a public forum.

Localization is interpreted with different requirements at each organization. What is your definition of it? What other requirements do you have that impacts localization? Lots of questions you need to need to answer first before someone can provide a solution. If you do not have expertize on this topic then I'd suggest hiring professional help to get a solid solution.