Mark Hazleton’s posterous

Good summary on SharePoint best practices in regards to Content Types and
Metadata definition.

With all the tools out there today, you need to plan a strategy on how you communicate with the public. Here is a blog post I'm working on for the new Social Media Tools community.

Good SharePoint wiki blog post.

Nice blog post on how to link web parts in SharePoint to create a richer experience.

Best Practices for SharePoint and Document Management. Great Stuff!

Compare WSS vs. MOSS

Side by side, feature by feature compare of MOSS and WSS, nice UI tabbed view

Hopefully most people know that MOSS is a superset of WSS. In other words, MOSS takes the foundation laid by WSS v3.0 and expands upon it, creating features that sit on top of it, utilize the core WSS framework, and extend it in such a way that is beneficial to larger companies, enterprise deployments, and portal scenarios. The following is a list of things that MOSS provides that WSS v3.0 does not. I figured it would be a waste of text to show the features that the two have in common, or the places in which MOSS re-uses WSS functionality without change or enhancement.

Yet another good overview of what MOSS has that WSS does NOT have. Nice in that it does not go over all the things that BOTH have. These are the "why go MOSS" points.

WSS is the third CMS I've worked with so far. As I've gotten more competent with it I can't help but compare it to some of the other products we've worked with in the past.

I was asked again by an acquaintance what I thought about SharePoint and if I though it's implementation was a good idea where he worked. He was struggling with what so many of us have been since the release of WSS 3.0 and MOSS 2007, and he asked the cardinal blanket question.

So what do you think about SharePoint?

The answer like so many things in development was "it depends". I won't even get into the differences between WSS and MOSS that's a completely different post. But I will try to speak to what WSS is good at as a CMS. Which is (to me) what the question is really getting at for most people (they're not even thinking of IPFS, Excel Services, Enterprise Search, etc...).

What WSS is Good At

WSS is a decent Content Management System. It's free with Windows Server 2003, provides a ton of features out of the box and once you get good at branding it, you can quickly customize new types of page layouts. It's of note though that to brand WSS you need SharePoint Designer (SPD) which is NOT free.

So what are some of the notable CMS features you get for free?

• RSS on pretty much all the content in the CMS.
• Versioning for content, and the ability to roll back to any given version.
• Publishing dates for content that let it go live and come down at a later date.
• Very throughout inheritable security that can be reset at many different levels throughout the site hierarchy.
• Good search.
• Alerts on content (when it changes).
• It's portable (you can migrate most site collections in less than 20 minutes).
• Good document storage (Document/Form libraries).
• Great integration with Office 12 (2007) products (especially Outlook).
• Good Blog and Wiki out of the box.

There's some others but those are the big ones that come to mind. It's also important to point out that for any ONE of these items I'm positive that you could find a 3rd party product that does a better job than WSS 3.0. For instance, the Wiki Site Definition is not as scalable or as powerful as a commercial Wiki engine. I think it's the combination of all these features that makes WSS a compelling offering. If you brought together MANY 3rd party applications you might have a dynamite offering, but it would be extremely difficult to integrate them all. You'd have to enforce a consistent user interface and bring all the content together under one search. This type of integration sows the seeds for collaboration which is is the direction most CMS's are going.

What WSS is Not Good At

I'm not going to lie to you, WSS has some pointy edges. Even with the plethora of documentation and blogs out there, it's very possible to feel like you're between a rock and a hard place when things go bad. Here are some of the things that out of the box that make WSS less attractive.

• It's heavy. WSS stands for Windows SharePoint Services...and there's a lot of them. If you do a complete WSS install we're talking about Search, Timer, Indexing...and I think there's more.. If WSS/MOSS is one thing it's heavy. Ensure you have some real hardware if you're going to install this beast, she needs a big cage.
• Difficult to troubleshoot. I have yet to do a clean WSS install (even with SP1) and not have the event viewer light up with errors. Even after spending a lot of time troubleshooting the event lot, I've never had a WSS/MOSS instance give me more than a day without kicking and screaming about something. You're going to need really talented and resourceful Admins if you're going to run this platform successfully. Hopefully this will improve over time.
• The WSIWYG editor out of the box is terrible. Not only does it not support image uploading but it completely breaks in Fire Fox and Safari. This makes it only really usable (out of the box) if you're in an intranet where you can shove IE down everyone's throat. Luckily there's free editors that do a better job, like this one.
• You need the Office SharePoint Designer. WSS may be free (with Windows 2003), but branding it isn't because SPD costs money. Unlike other CMS tools you absolutely need a proprietary tool to brand a WSS/MOSS instance. Your designer/web developer is also going to need to really know html and CSS. If you do have some people who know there stuff though you can get a really nicely branded site, an example might look like this WSS site.
• SharePoint is not great at housing web applications. There I said it. Yes you can get ASP.NET code to run in SharePoint, in fact there's a ton of ways to do it. All that being said though, it adds a lot of complexity to how your developers develop, deploy and maintain their code. At the end of the day you're often better off writing a separate ASP.NET application and just linking to it from your WSS instance if you need something that is not very CMS like.
• User experience. Even though I said that WSS provides a consistent user experience (as one of it's benefits) it's consistently mediocre. I have yet to have anyone I work say anything to the tune of "well that was easy" when dealing with Page personalization or WebPart management. It has a long way to go to catch up with the Ektrons or Clearspaces of the world.

Well that's more than a mouthful and definitely more than two cents. Don't get me wrong WSS has it's selling points. For a client who mostly wanted to manage web content and documents I would probably put WSS at the top of my list as an offering. For anything else I'd be more than a little reluctant to throw it out there as an option.

But hey, that's just me.

Good Luck,
Tyler

Excellent overview of SharePoint WSS as CMS features

SharePoint is the major player in Intranets these days. Good overview of what is going on in the Intranets Space from Jakob Nielsen

Interesting way to look at the vastness of Social Media platforms that are out there, Not sure it is the best way to approach the question of "What should I be doing". I'm interested in finding a Social Media Functionality Matrix that will help me develop my social media action plan for how to best leverage the sites that are out there. It is impossible to be all things to all people, but you want to engage your customers where they are.