It appears on the surface that SharePoint is intended to be used as a "live site" technology, where content is developed in the same place where it is published. For collaborative teamsites, this is often an appropriate model, since team members can generally be trusted with "half-baked" content. For content that is published outside the team, the built-in "publishing" feature (option) provides an extension of the develop-in-place model which hides draft content from readers until it is "approved".
However, there are many scenarios where develop-in-place is not appropriate; for example, when there is code involved as well as content, or where massive changes need to be coordinated to avoid large numbers of "did I update that link to the new page" questions. In these cases, some method of migrating content from a "development" server to a "production" server (or perhaps to some intermediate "staging" server) is needed.
Chris O'Brien, a Microsoft Most Valued Professional, does a thorough job of comparing the options in this blog post:
http://www.sharepointnutsandbolts.com/2007/10/stsadm-export-content-deployment.html
No comments:
Post a Comment