There is so much great content on MSDN, but often it's hidden away, so I like to blog about these finds so I have a chance to find them in the future.
Today's find is the Design Logical Architecture for Collaboration Sites.
In particular I like the advice surrounding team sites:
| Design guidance for team sites includes the following recommendations, each of which is elaborated in the following sections: -
Host team sites in a dedicated Web application. -
Apply Web application general settings, such as quota and life-cycle management settings at the Web application level to manage growth of team sites and to keep content current. -
Design content database settings for appropriate storage and scale and to ensure that you can back up and restore databases of the designed size. -
Automatically delete sites that are not used. -
Use paths to organize team site URLs. -
Plan for appropriate policies and permissions. |
Some of my notes:
- Hosting the team sites in a dedicated web app - This gives you the power to apply web application policy (this goes for the last point as well), what we normally do is have a zone like admin.yourteamsiteurl, then we use policy so that our administrators have full access over the web application. This means they can go into any team site if needed.
- In large organisations keeping an eye on the growth of the team sites is important, you need to know how large the content database is and when to expand out to more databases. Make sure you setup site level warnings, so your administrators are on top of the situation.
- Ensure that the procedures for notifying users of inactive sites is occurring, you really want to be able to claim that space back.
- A nice path is helpful for your end users, we normally opt for team.yoursiteurl/sites/<teamsitename> (the default setting)
This article also feeds into another great find Logical Architecture Sample Design: Collaboration Sites