Planning and Architecture for SharePoint 2010 – Start Your Engines

So I have been lucky enough to get to design an SharePoint 2010 implementation for a large school district. So since I’m a bit new to SharePoint I wanted to share this experience as hopefully it will be helpful to others. To start off, here is a quick outline of the major functions of the District’s site(s).

  • Main Public Facing Site – basically the commerical brand of the district with standard CMS type requirements
  • Intranet – holding all the custom application used for inter-office process and communication
  • Teacher Sites – used for direct communication between the client and the employee to share assets, create a simple means of communication, and event scheduling
  • School Sites – the sites that hold all the information related to a specific school. ** I broke this out from Teacher Sites for a reason, read on for details **

I broke apart the Teacher’s and School’s Sites for a couple of reasons.

1) I have been supporting “teacher sites” for a while and they tend to use the CMS in odd ways that could break the SP2010 cluster potentially.

2) Teachers move school so making this disjoint allows for simple updating of a school’s link the teacher site instead of re-creating the teacher’s site.

3) I prefer to have the resources broken apart so the school’s site performance isn’t impacted by the teachers.

4) Permissions will be simpler since “School Sites” will need a base set of permission unrelated to teachers.


I welcome discussion here. Please do comment on my reasoning here, as I’m sure different companies and schools different needs.

To get started on this planning phase, I downloaded the SharePoint Planning Book by Microsoft. You can get the PDF version in two parts here.



Here is another great link I’m using in the planning phase of this project. I plan to get some Visio diagrams posted in the next post to outline our architecture.

Planning on architecture for Windows SharePoint 2010