Gail Giacobbe, Principal Program Manager Lead and Ted Pattison, SharePoint MVP

• "Primary reason I don't use wikis is that we have so much information to track across so many sites that I simply can't keep track of them and forget they exist" as opening statement - not sure this is a real argument, can say that about any new tool not just wikis. Any new tool that requires behavior change can be a burden.
• Valid point is the need for wikis to support rich information (video, diagrams, etc) and need for compliance, audit, DLP, etc etc
• Enterprise Wiki leverages publishing infrastructure which powers Enterprise Wikis
• Note: should include differentiation from team wiki and deal with possibility that team wiki might be promoted to an Enterprise Wiki so how does that happen?
• Enterprise Wiki address the Community component of SP2010
• SP Foundation: Web Edit - easy page editing, wiki linking with auto complete, cross browser
• New site template for SharePoint Server build on publishing infrastructure - enhanced with categories, social tags and notes, page templates (content types and page layouts), ratings (web analytics) and customizations (master pages, CSS)
• Inherent content management, security, etc from SP2010 platform
• Wiki is an open publishing model - hmm, not sure I agree - it is an open collaboration space more than publishing - more community than publishing
• Demo:
  • Can insert web parts in wiki page
  • Can use rich text editor, insert graphics, use ribbon to change formats, etc etc
  • Good news - no wiki syntax and very easy to work with content as if it was a familiar document style
  • Rich content support is very straight forward
• Enterprise WIki is a publishing site - managed meta data, site provisioning causes group creation, metadata column automatically added, brand via master pages and CSS, cache scheme built in for scaling,
• Added new content type for wiki ...
• Enterprise Wiki can have multiple sub-sites ...
• Users will need to remember the different user experience, features and capabilities between the different types of "wikis" (enterprise and team) - that might prove to be a problem down the road from a design and user experience viewpoint.
• My Tweets during the session:
  • Nice demo in the sense of using a wiki style of content in an application context but not what you would think of as a wiki demo #spc09
  • Not sure I see this clear line between baby wikis and adult wikis (team vs enterprise) #spc09
  • I wonder if some of the distinctions between team and enterprise wiki are somewhat artificial based on underlying tooling #spc09
  • Seems that content gets locked into one wiki or the other - you need tomake the right decision up front and hope it doesnt change #spc09
  • So how does a Team Site with wEB Edit "wiki" get promoted to an Enterprise Wiki? #spc09
  • Interesting that "wiki" is implemented via publishing engine #spc09
  • Sitting in Customizing Enterprise Wikis in SP2010 #spc09