Comments on: Contextual Considerations of Technical Planning

By: Dan

Dan — Sun, 18 Jan 2009 23:32:59 +0000

Quite a good point. Check back soon for something along those lines

By: joelsef.blogspot.com/

joelsef.blogspot.com/ — Sun, 18 Jan 2009 21:49:23 +0000

Ah, good point. I apologize for veering off course a little.

Though you could say that good content planning affects the long-term health of a system, too. The more foresight you put into the content considerations, the less junk you’ll get to fix later on.

By: Dan

Dan — Sun, 18 Jan 2009 18:08:44 +0000

Joel – Definitely agree that the taxonomy and information architecture must also be in place. I suppose you could say that I was attacking this at more the “technical” angle than the logical or programmatic.

By: Contextual Considerations of Technical Planning | BH-Server

Contextual Considerations of Technical Planning | BH-Server — Sun, 18 Jan 2009 15:19:39 +0000

[...] here to review a rest: Contextual Considerations of Technical Planning Tags: architecture, deployment, environment, Microsoft, network, paco-de-lucia, point-saturday, [...]

By: joelsef.blogspot.com/

joelsef.blogspot.com/ — Sun, 18 Jan 2009 13:17:51 +0000

Coming from the front end kind of experience, I always make sure we have an initial content plan in place before building any sites or site collections. Call it taxonomy, information architecture, content structure or whatever. It may include content types off the bat, where it makes sense. Define sites, lists, libraries, templates.

This step isn’t unique to SharePoint deployments, but like with other platforms it’s often skipped or downplayed. Much like your tips above, a content plan isn’t required, per se. But if you skip this very important step you’ll have a lot of re-work down the road.

Sure, it’s probably time consuming to do this, especially if you’re anxious to get a site built and released. But at least have a basic plan (a few hours or a few days of analysis) vs. nothing at all. You’ll thank yourself later.