Help needed to design the branch

Hi,

I am looking for some help to design the branch and workarea structure to use SitePublisher. I know we can not have more than 1 workarea per branch to use the SitePublisher and here is my scenario:

Two braches. Internet & Intranet.
Internet branch users should not have access to Intranet branch and vice versa.
But both user should use a common area for their assets like images, js, css, some pdf files.

So what is the best solution to structure this? Can I have something like this:

main
     common (sub branch)
             workarea
                    common (workarea folder) 
                          assets (folder)
     internet (sub branch)
              workarea
                     www (workarea folder)
                            sites (folder) 
     intranet (sub branch)
              workarea (workarea folder)
                     www (workarea folder)
                            sites (folder)

Or we should have those assets available at the sub-branch level?
Thank you.
John

Find more posts tagged with

Comments

sheikh1

Recently in our forum there was a similar thread posted and lot of valueble coments came out in that, you can search for that thread or I will post it here back if I found.

Going by your approach provides security and authorizations as per your requirements but you cannot achieve asset sharing between your two branches.

I would suggest you go as per the sitepublisher recommendation of having two sites in the same branch/workarea. for ex: and you can have common assets sharable by two teams.

main/company/workarea/www/common-assets
main/company/workarea/www/sites/intranet
main/company/workarea/www/sites/internet

You need to add few lines of code in your submit config file to set correct group permissions when ever new content items were created or submitted so that one will not step into others foot.

Adam Stoller

Continuing along sheikh's suggestion ...

To handle the security restrictions for the content (DCRs, Pages) consider:

The use of the first two is hopefully self-explanatory with respect the top list of things to consider; the use of the latter would be for all shared locations within the branch (e.g. the workarea, the root of the workarea, images folder, css folder, etc.)

Rick Poulin

Multiple sites in a single branch is the way to go UNLESS you have additional requirements that you haven't mentioned. For instance, if your Internet vs. Intranet have distinct runtime targets, then you'll have an easier time configuring your deployment if the sites are in separate branches.

LooseCannon

My TeamSite branching structure is similar to what you have proposed - except we use separate stores for Intranet and Internet due the number and size of our Intranet and Internet sites.

We have several Internet sites that share common web assets that are managed out of a "Common" branch. Each site has it's own branch to allow editors and reviewers access to specific sites. Security trimming access to files is much simpler at the branch/workarea level than the folder level.

Our solution for accessing assets in the Common branch from the site specific branches is with symbolic links. If sym links are not an option then you could have a process that copied the assets from the Common branch to the site specific branches - this will of course result in duplicate files which may or may not be an issue.

Topic_37679__Create New Rows using Scripted Data Source__cwong.rptdesign

jstephan

Thank you all for your great responses. I really appreciate your inputs. To all +++

The business rule is that, the internet group should not have even read access to the intranet folders in respect to content and viceversa. But they would share some common images, css, js.

HTML5 Chart -- Bar Chart Resize on initial and browser resize__cwong.rptdesign