/bin/tim

I love SharePoint and I hate it too.  Its great in concept, but often so rigid in structure when creating a project.  I’ve often thought why not just code the site in ASP.Net when designing a SharePoint solution, but I usually end up with SharePoint because it just has some handy bits and so many corporates are familiar with it.  I usually struggle explaining SharePoint to some customers as its more a dev tool than a solution and its only when we deliver a KM or CMS solution that people get it, or at least understand what it did.

I just saw this article in TechNet magazine about SharePoint as a Wiki, which is a great concept, but one I thought a bit out of SharePoints scope but its interesting.  I’m not convinced about the presentation, but the editing tools are there.  Seeing this would not necessarily encourage me to use a Wiki as a knowledge management tool, but at least its supported in concept.

So now SharePoint can be a Content Management System, and Knowledge Management solution or even a Wiki.

More here http://technet.microsoft.com/en-gb/magazine/cc162514.aspx