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

how to structure localized websites in Teamsite

Frederik

Hi folks,

Our "business people" have decided that our site must in future be available in many more localized versions and languages (~12) than it is now (3). This fits in a larger project of migration.

Currently, we have 3 languages (combined with 3 countries, giving 6 "editions" of the site). For each content item, there is one DCR with replicants at the top level, for country and language. Template.tpl files output all the "country_lang_data.xml" files, to be read/included by an application server. Content contribution is centralized to a few people entering these 3 languages.

Future is 12 languages. Content contributions will be centralized at first, but decentralized as soon as technology/management allows. There will NO longer be just 1 DCR for all language-version of a content item, but 1 DCR per language-version.

The structure of the sites will be common (structure reuse), but _content_ reuse will only happen for some content types (e.g. some news articles; and layout elements), as most content will be translated/localized.

*** QUESTION *** We are currently looking at data structuring, and precisely: should we use BRANCHES to separate localized content, or use ONE BRANCH and SUBFOLDERS to separate localized content.

That is (MULTIPLE BRANCH):  

Project-BR
     +-- uk-BR
            +-- /xmlToDeploy/sub-section/'file'
            +-- /templatedata/Category/Type/data/'dcr'
     +-- fr-BR
            +-- /xmlToDeploy/sub-section/'file'
            +-- /templatedata/Category/Type/data/'dcr'
     +-- de-BR
            +-- /xmlToDeploy/sub-section/'file'
            +-- /templatedata/Category/Type/data/'dcr'

or (ONE BRANCH): 

  Project-BR
     +-- WA
          +-- /xmlToDeploy/uk/sub-section/'file'
          +-- /xmlToDeploy/fr/sub-section/'file'
          +-- /xmlToDeploy/de/sub-section/'file'
          +-- /templatedata/Category/Type/data/uk/'dcr'
          +-- /templatedata/Category/Type/data/fr/'dcr'
          +-- /templatedata/Category/Type/data/de/'dcr'
          +-- etc.

What important benefits and difficulties can we expect? What have you learned from your experience?

I've currently defined following areas of impact that might be worth to investigate:

- development and maintenance
   - configuration of Teamsite and customisations
   - tpl, dct
   - security

- end-usage
   - process for sharing content
   - content management (day-to-day usage) / if centralized / if decentralized

Are there other areas impacted?

All input, stories, wisdom, experience welcome

Thanks! Frederik.

Find more posts tagged with

Comments

gzevin

Ohmygod.... you are asking a few thousand dollar question Smiley Happy

)

Seriously, I would not put any reccomendation as one, to make a qualified opinion, needs to conduct a serious excersise, that would include talking to business/web developers/stakeholders....

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Frederik

In reply to:

Ohmygod.... you are asking a few thousand dollar question )

haha :-) Thx for the feedback, I guess I asked a bit too much then :-)

Let's just rephrase as such : what's your experience with multiple localized sites, in one or separate branches. Lessons learned? Wish you had done it differently?

The only thing I found on devnet so far, is this one (about multiple branches, it's not about 1 site - localized content):
http://devnet.interwoven.com/forums/cgi-bin/showflat.pl?Cat=&Board=PRODUCTS_TEAMSITE&Number=5980&page=&view=&sb=&o=&vc=1

Capture.PNG

Bowker

There are a few other issues/configurations to consider:

How are your web servers setup? (one docroot or multiple?)
Are you using OpenDeploy to push files out? (support of multiple deployments for different versions - or maybe parametric deployment)
Do you want to separate regional/languages to allow for different groups to maintain? (security concerns)
How big is the site? If the site is HUGE then you may want separate branches or even backing stores.
What would be more 'end-user friendly'? Training and support is always a concern.

Good luck.

Dan Bowker
Northern Trust
Web Publishing Technology

gzevin

well, I'd say that I would choose multiple workareas and multiple branches, but aagain, this depends on the business process, workflow needs, users' eacceptance of the workflows, content reuse, etc...

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

3.PNG