How did Microsoft ever come up with the plan to integrate CMS into SharePoint in O12? Gerhard tells!

Friday, January 20, 2006 5:32 PM

[via SharePoint Team Blog]

Gerhard Schobbe, Group Program Manager for the CMS Team, added a lengthy comprehensive post to the SharePoint Team Blog today that goes into the details of how Microsoft came to the decision to integrate CMS and WSS, or as CMS will be known (at least as it is today) in O12 as Web Content Management (WCM). To start, he details the three high-level goals:

  1. Provide much deeper integration between CMS and SharePoint functionality.
  2. Make creation of dynamic, highly customized, content-centric web sites dramatically faster and easier
  3. Address the miscellaneous collection of 2nd order (compared to the call for integration) feedback that had collected up.

How they team addresses these goals and the evaluation process of how to “rewrite” CMS to include all the needs of customers vs. having CMS be more closely integrated with WSS (that is, O12 WSS… or WSS v3). WSS provides a ton of things OOTB for CMS:

  • Versioning
  • Check-in/check-out
  • Backup/restore
  • DAV support
  • Security
  • Recycle bin
  • Alerts
  • Storage (WSS is already scalable to “handle hundreds of thousands to millions of items”
  • Personalization
  • Search
  • Workflow

He goes on to discuss other items close to CMS developer’s minds such as transistioning their current MCMS environments to O12 WCM:

  • Migration (both content & custom code) from MCMS 2002 -> WCM in O12
  • MCMS 2002 PAPI forward compatibility (spoiler: it won’t be)

It’s a fantastic read for anyone who works with MCMS 2002. 

However it begs a question from this CMS developer: Why is this on the SharePoint Team Blog and not the Web Content Management in Office “12” blog? Did the WCM team lose the password? I’m guessing we won’t see much form the latter in the future, so you CMS’rs, jump on the SharePoint bandwagon.

» Content Management Server and SharePoint

comments powered by Disqus