How many barnches and sub branches

Hi all,

I was just wondering which is the best design approach

1)One branch and many workareas in tht branch.
2)One branch and many sub branches each having one workarea.

can some one throw some light on the pros and cons of above two design approaches.

I have to implment a scenario in which "All the contents are organized in one single branch. This branch has one site per country/language combination."

What all issues will be there in this kind of implementation?.
Is this a good design approach?

Find more posts tagged with

Comments

curiousmaverick

We are inplementing the second approach. Our scene is something like many microsites under one umbrella. So one subbranch for each microsite and one workarea per subbranch.

Regards,
Mav

scgv.rptdesign

Frederik

we have done both...

in one occasion, the country sites are independent, and need to be deployable separatedly. => sub-branches

in another case, the sites are much more integrated, and content is exact match, just translated. => 1 branch, 1 WA.

It all really depends on your circumstances, and the need to isolate content and users from each other; and the skill level & dedication of contributors.

the 1 branch, Many WA model does have one CAVEAT: you need experienced contributors to deal with the getLatest (synchronising) of content to other WA, and deal with submit conflicts etc. Also, if you have processes running against WA content, that may need to be duplicated per WA (in some instances, we run full-text indexer against WA content to have accurate search preview on backend - it's not ideal, but just an example)

moonkhanna

Hi all,

I was just wondering which is the best design approach

1)One branch and many workareas in tht branch.
2)One branch and many sub branches each having one workarea.

can some one throw some light on the pros and cons of above two design approaches.

I have to implment a scenario in which "All the contents are organized in one single branch. This branch has one site per country/language combination."

What all issues will be there in this kind of implementation?.
Is this a good design approach?

At our end, we implemented your first approach and now moving to the second on another project. As I indicated yesterday on another post from you, this is really your choice. Both the approaches work well. Preferable is your First Option but painful as implementing permissions in that scenario is complicated and calculative. Also, when the Business areas are totally separate, it does not make much sense to have everyone on the same branch.

Then are your preview requirements. Is there a case, when someone wants to validate links within Teamsite? and Finally the Publishing cycle and your Revision History requirements.

ISCBorisB

Hi all,

I was just wondering which is the best design approach

1)One branch and many workareas in tht branch.
2)One branch and many sub branches each having one workarea.

can some one throw some light on the pros and cons of above two design approaches.

I have to implment a scenario in which "All the contents are organized in one single branch. This branch has one site per country/language combination."

What all issues will be there in this kind of implementation?.
Is this a good design approach?

You may want to take a look at [thread=18866]this[/thread] thread.

nipper

Tossing my $0.02

There is no 1 size fits all answer. Everything depends on the needs of the project, type of users, number of users, etc.

That being said. I will typically start with 1 main branch, several sub branches and 1 workarea per branch unless I see a compelling reason to change.

If you read the link Bo pointed you to, you can see convoluted decision making process that makes a clear answer difficult.

RonaldV

Yes, this is why they pay us, Teamsite consultants, big $$$.