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

multiple language site support

Abhishekghosh

Hi All,

This is more of a Brain storming Question and i would As many people to post their answers as possible ...

I want to know if there is a website and it need to be compatable with N Number of Languages with respect to Teamsite.

What will be the best Approach with Architect point of view ...

As per me the normal tendency will be either create seperate folder for different languages or create a single folder and have database take all the date and simply show it in website but drawback is not all know english.

Is there any other way with respect to Architect Point of view , which anyone of you have worked on mutiple language functunality.

Regards,

Abhishek

Find more posts tagged with

Comments

Rick Poulin

Are you talking about localizing your website, or localizing the TeamSite interface?

Are you using SitePublisher or not?

Abhishekghosh

Hi,

Yes that is a valid solution as Livesite and Site Publisher is an Option but issue is that client has agreed only on Teamsite as of now that is a contraints because we will need seperate licence for livesite.

Abhishek

Snap 2016-09-08 at 16.37.08.png

Snap 2016-09-08 at 16.39.08.png

Snap 2016-09-08 at 16.40.18.png

Snap 2016-09-08 at 16.42.50.png

GroupingAndCrosstab.zip

Abhishekghosh

Sorry Just adding to My above comment , the client has a sites which are in different langiages but now they want to use Teamsite for these websites , so it is like a migration of websites to Teamsite.

Rick Poulin

Ok. Well the traditional approach is to separate localized content into different sub-branches, and keep the "common" stuff like CSS and JS in the parent branch. This, however, assumes that you're not sharing a whole lot of content between them.

The alternative is to have all localized content in the same branch and use subfolders to store localized versions. This is the approach you want to take if you're thinking of introducing LiveSite in the future. Also, with this model, TeamSite has some native functionality which can help manage your localized copies. It has its quirks, but that could get you a running start.

To use the native functionality, go to the branch and then Configuration > Locales. Add the locales for your site; you can add more later. You MUST define one locale as being the master. That means all new content must be created in that language first, and then the localized copies are created from that version. So, go into your branch, create a new DCR, save, and then use Actions > Localize. There's also a baseline workflow example to help manage status, and a Actions > Manage Localization overview of your content. Surely this is explained in documentation somewhere, but I don't remember seeing it.

Abhishekghosh

Hi Really !!! Thanks .. You have given me a direction as i have never explored this part of Teamsite , i am aware of the inside but something like this is great .. Is there PDF or DOC where i can get more details on this ....

Please guys if you have something to share i will be greatfull Open to all point of views ...

Rick Poulin

Your organization should have access to the support portal, where you can download the documentation.

Abhishekghosh

Hi,

I was trying to Use the Globalization workflow but i think the issue is stuck at the commad

Do we need to configure this or is something missing in the tags ...

Abhishek

Abhishekghosh

Hi All,

Issue us solved the WFM is Up ...

Abhishek

Rick Poulin

You should post details of the issue and your solution, in case someone in the future comes along searching for an answer to a similar problem.

Abhishekghosh

Hi ,

The issue was that the command tag in the available_model was in cap that why i was getting an error, as it was a silly mistake didnt post it ... but sometime small things gives big solutions Smiley Happy

get2RPT.png

getRpt.png