Sites and Templates

Use the top level site as a "front page" for rolling up information held elsewhere dependant on the user. Use the Audience capability in Sharepoint for information targeting (eg News).

Other sub-areas:

Students

Staff

Classes

Think about how you catagorize things.... for navigation and site layout. Generally, it is not a good idea to have lots of subsites under one site. Branch it out.

Egs....

Staff

--Departments

--Staff Room

Classes

--Year

--Subject

Subject

--Technology

--ICT...

Technology

--1A/NG (classes)

1A/NG (Classes)

--Blog

--Wiki

--Lessons

Courses and Resources

-Teacher Aids

-Exercises

-Subscribed Content

-Library

-Subject Resources

Architechure: Difference between Sites/Site Collections

Site Collection:

Galleries

Features

Security

Search

Auditing

(ie. Applies to all....!)

Sites:

Lists and Libraries

Features

Tempates

(ie. Applies at this level only....!)

Database:

DB per site Collection

Scenario...

Site: Classes (and any sites below the top level)

Inherited from School Site

Contains:

Lists and Libraries

Features

Templates

Allows you to:

Break inheritance (at a site level or on a list/library, or an item - bear in mide the performance impact whilst it checks if you have permission on loading)

Customise, and doesnt work back up the tree.