Windows Server

Deb · Guest

I would appreciate online references to information to study relative to best
practices when planning the organization of site collections. I would like
to understand what the issues are to take into consideration when deciding
whether to make sites parallel in the hierarchy or subordinate to another
site, etc.

For example, we have the need to have one site be "public" in the sense our
entire organization needs access to documents and information on that site
developed for policy and procedure documentation. Then the department itself
needs a private site for its intra-departmental procedures. Someone else set
up the sites and made the public site a sub-site of the private site. My gut
tells me that's a bad design since it prevents a public visiter from taking
advantage of the site navigation provided by the links in the upper-right
corner that traverse the hierarchy.

Thanks!

Heather Solomon [MVP] · Guest

I don't think I have ever seen a published study like that. You can look
around these resources and see if there is anything you can use:
http://heathersolomon.com/blog/articles/148.aspx#Plan

I agree with you though that the current setup is a bit backwards. In
addition to what you said, if documentation is a key focus of the public
site, document workspaces under the public site may work better for file
management of updates and the like.
--
Heather Solomon, MVP WSS
http://www.heathersolomon.com/blog

"Deb" wrote:

	Windows Server Forum Index -> Windows Services	All times are GMT
Page 1 of 1