best path to follow?

CRB

Hello,
i have question to the experienced guys on here about the best way to do this:
the production team is using teamsite to maintain/develop website A...
so TS structure is like this:
Branch A > subbranch a1
> subbranch a2
they devolop content in a1 then once finished, it is moved to a2 and then generate edition from a2 to push it to the live server...
now we have a team who will be working the next few months in new feel and look of website A... we created a workarea for them under a1... but i dont thing they can push thier content to stagin to preview it, because we dont want them to overite the content right now. so my concern is that i dont want anything they create to overite what the dev team creates now since we are not changin the site yet.
my suggestion is to create new branch B and work on it. and get latest from branch A to stay in sync while changin the look and feel. but that will cause paths to change, and we dont want to go throu changing links as we get latest? and when want to start using the new site...

what is the best way to accomplish change the feel and look of a site without causing the two teams to over eachothers (maybe separate branchs) also with the minumun change in paths? and remmeber that both teams will need to get latest from the same spot. just one of them will work on it as daily task for the site A.. the other team will be working on changing the look and feel.

as always your input is very appreciated!

Adam Stoller

Hello, i have question to the experienced guys on here about the best way to do this: the production team is using teamsite to maintain/develop website A... so TS structure is like this: Branch A > subbranch a1 > subbranch a2 they devolop content in a1 then once finished, it is moved to a2 and then generate edition from a2 to push it to the live server... now we have a team who will be working the next few months in new feel and look of website A... we created a workarea for them under a1... but i dont thing they can push thier content to stagin to preview it, because we dont want them to overite the content right now. so my concern is that i dont want anything they create to overite what the dev team creates now since we are not changin the site yet. my suggestion is to create new branch B and work on it. and get latest from branch A to stay in sync while changin the look and feel. but that will cause paths to change, and we dont want to go throu changing links as we get latest? and when want to start using the new site... what is the best way to accomplish change the feel and look of a site without causing the two teams to over eachothers (maybe separate branchs) also with the minumun change in paths? and remmeber that both teams will need to get latest from the same spot. just one of them will work on it as daily task for the site A.. the other team will be working on changing the look and feel. as always your input is very appreciated!

Sub-branches for future development work is probably the way to go.

Syncing the sub-branch with current development is never a trivial task, and you cannot update a workarea on a sub-branch directly from the staging area of a parent-branch (Interwoven never created real relationships between branches and sub-branches - a sub-branch is, in most cases, identical to a sibling branch - except when dealing with path regular expressions used for controlling other aspects of the product)

If the changes are limited to look-and-feel and the site is templated - then it should just be a case of changes to PTs - which could be done within a separate workarea on the primary branch - or it could be done in a sub-branch where the sync'ing of the content is handled via a process that explicitly excludes trying to update PT code from the parent-branch to the sub-branch.

You need to develop the design carefully first before you try to implement it - otherwise you're likely to walk into a lot of "walls" as you try to make things work and the end-result will probably be very difficult to maintain.