views:

60

answers:

3

Hi all,

I'm looking for recommendations for books to help my two-man team in planning our Sharepoint intranet site. I have worked with Sharepoint some before, but for a site with only about 30 users. This one is going to end up with about 1500 and my head spins trying to think of where to start.

It seems like there are dozens of books out there telling me the "how to's" of Sharepoint but what I really need to know is the "why's", as in "Why use a Publishing Site instead of a Team Site?" or "Why use multiple site collections instead of one site collection with a lot of subsites?"

Any and all recommendations are greatly appreciated.

Z

+1  A: 

Technet is pretty good, however it might be wise to supplement those articles with various books depending on the gaps in your knowledge.

Look at this: Planning and architecture for Office SharePoint Server 2007

When you have particular questions ask on forums, or team up with an expert in implementations who can advise you when required.

Regarding your two questions:

  • Why use a Publishing Site rather then a Team site? It depends on the functionality you require. Create a demo Sharepoint environment where you can setup sites with each template, and try out their functionality.
    Typically you'd use a Publishing site when a small set of users is publishing data to others. While you'd use a Team Site, when a group of users is collaborating together.

  • You'd use multiple site collections if your estimations of the size of the site collections indicate they'll breach the limits of Sharepoint (Roughly 100GB depending on hardware.), or if they have different management teams.

Bravax
Hi Bravax, We've looked at the linked document to excess. It's still not asking several of the questions we're asking. For instance, just from reading your reply I think "So should each company department have it's own site collection? How do you tie navigation and search together on a top level site?" There's a couple thousand in our heads like that :)
zakster82
Yes, that's generally what happens. (More questions then answers being generated...). It depends what you're trying to do. We're going the route of each company department having it's own site collection, but this isn't necessarily right for you. We're modified the default navigation, using a custom XML/AD group config.
Bravax
Bravax - can you elaborate at all or link to what you're talking about with the custom XML/AD group?IrishChieftain - This site will be for 1500 users across approx 35 departments. That makes me think more site collections is good, even if a pain. Thoughts?
zakster82
Sure, I was looking it up. Look into MossMenu. See: http://blogs.msdn.com/ecm/archive/2006/12/02/customizing-the-wss-3-0-moss-2007-menu-control-mossmenu-source-code-released.aspx
Bravax
That's quite afew departments, so management could get messy for that number of users. How many documents will go into it? Do some capacity planning.
Bravax
I barely even know what capacity planning means. Ugh. The trouble is that no one has too good an idea. It's going to start as an intranet site for IT and then use that as a springboard to "sell" Sharepoint to other depts. I'm trying to keep us from shooting ourselves in the foot down the line. I could see each department using from 100MB to 5-10GB of documents. But realistically that's a wild guess. Nobody has really been able to answer that.
zakster82
So start with one site collection for IT and go from there. You don't need to plan too far ahead, as long as you build some flexibility into your hardware, and design. You can check existing file servers for a rough guide to how much might be uploaded into sharepoint.
Bravax
Thanks Bravax. I'll give that a try.
zakster82
+1  A: 

Our team has copies of several of several books, and they've been very helpful. Here's a few.

Beginning SharePoint 2007 Administration

Pro SharePoint Solution Development (for developers)

Microsoft SharePoint Unleashed

Kyle Trauberman
+1  A: 

'Professional SharePoint 2007 Web Content Management ...' by Andrew Connell is by far the best book for what you are facing - I just completed an Intranet for 800 employees and I had to learn this stuff from scratch - this book is what really helped me:

Professional SharePoint 2007 Web Content Management Development: Building Publishing Sites with Office SharePoint Server 2007

Each site collection is its own administrative entity. And each time you add a new site collection, you are doubling the admin workload if you are the ones responsible for the admin. For 30 users, stick to a single site collection unless the governance explicitly calls for something else. More site collections can also mean more down time when backing up and restoring :-)

Here's another piece of advice: don't even think of going into production until you have verified and documented your backup and restore process. In fact, I created a team blog to document everything I did. The definitive guide to backing up and restoring:

'SharePoint 2007 Disaster Recovery Guide'

If your site is going to involve much coding, then you will need to look at 64-bit as that is the only platform supported as SharePoint moves forward.

IrishChieftain
Somewhat off-topic, but any idea if there will be an upgrade path from SharePoint 2007 32-bit to SharePoint 2010 64-bit?
zakster82
Re-install all the servers, and migrate the content? Seriously if you're looking at a new SharePoint environment, I would go with 64-bit now.
Bravax
Migration seems to be well documented:http://bit.ly/3Yzk10 There will also be a wizard to upgrade your VSE solutions. My only concern right now is the CSS "implications" of the new look and feel in 2010 publishing site.
IrishChieftain