How to get over the 'OOTB syndrome' for MOSS WCM
I rarely rant, but in some cases I have very little choice. As it seems I had little choice but to rant at this question, statements that I was confronted by time and time again. I call this the “OOTB syndrome”. This is usually a symptom which is present in people who have stumbled upon SharePoint recently.
In the context of this post SharePoint = Microsoft Office SharePoint Server = MOSS
“We want to use the Out of the Box (OOTB) functionality of SharePoint to build our web site”
“SharePoint templates are not XXXX compliant”
“It’s too difficult to build web sites with SharePoint”
First of all MOSS provides example site templates to provide “examples” of how to use SharePoint for WCM (Web Content Management). These are simply that “examples”. If your organisation is looking at building a web site with MOSS then you will need to consider these points.
Also in a previous post I mentioned about how to approach customizations.
**Spencer Harbar from harbar.net has provided his view on this here: **http://www.harbar.net/archive/2007/06/21/SharePoint-Egg-Timer-1-quotWe-want-a-SharePoint-site-that.aspx
The bottom line is if you are looking to just build a web site you may be better off getting an alternative which just does it. There are tons out there. SharePoint is not Dot Net Nuke, it is not MCMS (Microsoft Content Management Server), it is not Ektron, it is not Interwoven or Epi Server. It’s a technology platform upon which a multitude of applications are built. It’s more akin to ASP.NET than to a “competing product” that in reality only competes in one or two feature areas.
But if you are looking for a standardized solution platform that can deliver multiple web sites and enhanced publishing features then MOSS is a very good choice.
If you are starting to build a site on MOSS consider these points…
It’s easy for backbenchers to whinge about SharePoint does not do X or Y, but for people who take the effort to understand and learn core functionality and API the benefits are huge in terms of becoming an expert in SharePoint as well as understanding the breadth of the capabilities.
Here are some “real world” case studies of MOSS WCM implementations.
MOSS Has Got Game - Glu Mobile’s Website (www.glu.com) - How We Did It - Part 1
MOSS Has Got Game - Glu Mobile’s Website (www.glu.com) - How We Did It - Part 2
How we did it: PFGC.com — design, development, and go live in 10 weeks!
Plymouth Hospitals: This site is WCAG 1.0 AA compliant and provides colour contrast and font size options for the visually impaired. To build a site like this in SharePoint the starting point has to be at a custom site definition plus building some smart web parts to render compliant mark-up. The beauty of the SharePoint platform is that it’s possible to do these things because it’s built on ASP.net.
Hawaiian Airlines: Extreme “Bling” to your SharePoint site by giving it all the latest such as reflections and so forth, where the goal is to entice end users to buy air line tickets or visit Hawaii. This is built as a Publishing web site, which is delivered by the WCM features of MOSS and is primarily an Internet facing public web site.