

You can create new site templates, and you can modify a site based on a site template to be completely different from the initial default state. This defines what master page, webparts, content types are available by default initially for a new site. So this is one of the basic building blocks within Sharepoint. Reuse of a custom list item on other sites requires that you create a content type. Workflows are best targeted at content types. For example, data retention policies are best targeted at content types. A large set of the “global” functionality within Sharepoint is targeted at content types. So every “item” within every list in sharepoint has a content type, e.g. Content types are the schema component within the data architecture of Sharepoint. If you’re like me last week, you probably don’t know what they are.

Most everything revolves around content types. There are some fundamental, basic building block, kind of objects which define what most users see and experience.Almost everything in Sharepoint is a list or an object in a list.There are some exceptions and it’s the exceptions which often drive architecture. Almost everything in Sharepoint is stored within a SQL database.So there are several fundamentals you have to understand about Sharepoint : But for the first time, I’m starting to get a sense (dare I call it a vision?) for what the Sharepoint architecture might look like here at the UW. This is really hard to get with something like Sharepoint, where the feature set is so large. The funny thing about such a “big picture” focus is that it requires both a breadth and depth of technical detail. Like everyone else, I’m interested in learning what the buzz is about, but I also bring a focus which is very architecture-centric–the “big picture” if you will. With a bit of my time opening up with the advent of the Nebula domain migration put on hold, I’ve been really digging into understanding Sharepoint 2007. So expect a torrent of sharepoint related info here soon. But don’t worry about missed content, because I’m going to re-post all that stuff here (sorry about duplication, but I think it makes sense for the content to be re-accessible). If you aren’t subscribed, you should consider getting on that list. Over the past week, I’ve been posting like mad to the sharepoint_tech mailman list.
