Sean Wallbridge, SharePoint MVP


RSS Feed Feed your read!

The Lowdown

Sean's Resume
itgroove (Victoria, BC)
Major Change
Beer Me! (Donate)
Sean's SharePoint Ditty
About Sean
SharePoint Best Practices
Recommended Reading
Follow me on Twitter
Aggregated MVP Blogs

Search

Archives

August 2010 (4)
July 2010 (6)
June 2010 (4)
May 2010 (16)
April 2010 (20)
March 2010 (11)
February 2010 (3)
January 2010 (4)
December 2009 (6)
November 2009 (5)
October 2009 (14)
September 2009 (15)
August 2009 (11)
July 2009 (14)
June 2009 (20)
May 2009 (19)
April 2009 (22)
March 2009 (20)
February 2009 (19)
January 2009 (13)
December 2008 (8)
November 2008 (16)
October 2008 (16)
September 2008 (16)
August 2008 (11)
July 2008 (5)
June 2008 (8)
May 2008 (14)
April 2008 (18)
March 2008 (31)
February 2008 (13)
January 2008 (10)
December 2007 (4)
November 2007 (2)
October 2007 (9)
September 2007 (10)
August 2007 (4)
July 2007 (10)
June 2007 (7)
May 2007 (13)
April 2007 (8)
March 2007 (1)
February 2007 (2)
January 2007 (11)
December 2006 (2)
November 2006 (10)
October 2006 (7)
September 2006 (5)
August 2006 (6)
July 2006 (5)
June 2006 (5)
May 2006 (5)
April 2006 (7)
March 2006 (2)
February 2006 (3)
January 2006 (9)
December 2005 (4)
November 2005 (19)
October 2005 (6)
September 2005 (15)
July 2005 (5)
June 2005 (3)
May 2005 (4)

Links

itgroove Website
BrainLitter Archive
SharePoint Team Blog
Sean's SharePoint Ditty
WSS 3.0 Builds
MOSS 2007 Builds
MVP Profile
MCP Virtual Transcript
2010 Product Comparison

Tag Cloud

Active Directory, ASP.NET, Best Practices, CKS Enhanced Blog Edition, Exchange, From the Brain, IIS, ISA, itgroove, MOSS 2007, Outlook, Rants, Response Point, SBS, Security, SharePoint, SharePoint 2010, SharePoint Designer, SQL Server, Terminal Services, Toronto Maple Leafs, VMware, Web Litter, Windows, Windows 7, Windows Server 2008, Windows Vista, WSS 3.0,

Building a Knowledge Blogging System in SharePoint - A simple, but effective method of replacing key office email correspondence with a SharePoint blog 

Tags: MOSS 2007, SharePoint, WSS 3.0

Internally, we are using SharePoint blogs very effectively, to replace common sharing of information (in our case, typically about technology like 'how I fixed this or that'. Using Microsoft Word 2007 as our blogging tool (and if you don't have Microsoft Word 2007, you could use Windows Live Writer, which is free), and SharePoint (MOSS or WSS) as our blogging engine, we have all that we need to create a rich, blogging experience with the following benefits:

 

  • We create/share information using a rich tool, just like composing an email to the team (A subject, some paragraph/body text and maybe some clipart, screenshots, etc.). However, this information is retained within SharePoint, meaning it is not lost in Sent Items – it is searchable and discoverable within SharePoint (by search or category lookup). As well, as you'll soon see, as we have subscribed all staff to Alerts, regarding new content, we also receive the latest blog information, real time. By storing the information in SharePoint, we also get the added benefit of this information being available to NEW employees as they come on board (again, not lost in someone's thoughts, memos or Sent Items bin)

 

To create our Office 'Knowledge Blogging System', we take the following steps:

  1. Create a blog site (we have two, 1 for technology issues where categories are based on topics such as different types of technology, and another blog whose categories are actually the names of the various clients we support). In this example, I'll be creating the blog for 'client support' (categories, named after clients)
  2. We'll change the behavior of how posts are moderated. By default, a blogging list in a blog site will require posts to be approved. We'll turn that behaviour off (we're a small team, of 5 people), we are looking for 'speed' of information instead – your environment may be different or the content may be more sensitive
  3. We'll set blog alerts so that when a new post is created, everyone receives a 'blog notification' which is basically the entire content of the post, as an email – i.e. this would have been the typical 'hey guys, I learned this, try and retain it' email and where the life of it would have stopped. Instead, everyone gets the email as a byproduct of saving the content into SharePoint – now and for the future
  4. Create the necessary categories (in our case, these will be names of clients we support and store information about)

 

Simple, effective and awesome, I think anyways.

 

Step 1 – Create a Blog Site

 

In this instance, I'm going to create site underneath our 'client management' site. The steps to create a blog site are really straightforward and illustrated in the next few screenshots:

 

 

 

 

Now we have a blog site, ready to roll. Style it/theme it in whatever manner you want. The next step is to click 'Manage Posts' and change the default 'approval' behaviour to allow posts to be posted immediately (none of that pesky approval process, for our small team/content).

 

2. Change the Approval Behaviour for posts to not require approval

 

 

Choose Settings, List Settings and then select Versioning settings.

 

 

 

3. Configure the list to set all necessary staff to receive Alerts (emails) of new posts

 

You may have a different way you will want to approach this (such as a workflow, etc.). However, the quick and dirty way to enable everyone on your team to receive the latest blog content (knowledge!), is to subscribe them to alerts, from the Blog Posts list.

 

Simply open the Blog Posts list, choose Actions, Alert Me and set the appropriate notification settings. For us internally, sending alerts when 'New items are added' made the most sense. See below for the visual steps necessary:

 

 

 

 

4. Create your categories

 

In our case, for this particular blog (again, we employ two different blogs, your mileage and use will vary), our categories will be defined as the clients we support. For the purposes of this blog entry and confidentiality, I've made up a few… Click on Categories and change the defaults (Category 1, 2, etc.) and add any additional categories you made need.

 

5. Register Microsoft Word 2007 (minimum) as your Blogging Editor (or download, install and configure Windows Live Writer, which is out of scope of this post)

If you don't have Word 2007, Windows Live Writer is a great, SharePoint capable Blogging Tool. I happen to prefer Word 2007 (SmartArt anyone?) but Windows Live Writer is free and there are lots of cool add-ons for it, that you can't get with Word. And if you have Word 2003 or older, Windows Live Writer will be the tool you want to seek out. (Get it here: http://download.live.com/writer)

 

Simply click on 'Launch blog program to post' if you have Word 2007 locally installed.

 

 

And then accept the various defaults (or change them, I don't care :)

 

 

 

6. Finally, post away and enjoy the result

 

In Word (or Live Writer), blog away – always be detailed and don't be afraid to add illustrations to make your point – that's the beauty of using Word (and SmartArt) for providing clear messages. Here's a basic sample, but you'll get the picture. And, the net/final result is your team will receive an email with the blog post (just as though you sent them your informative/knowledge email), but you'll have the added bonus of a blog post that is permanent and searchable as well (future proofing).

 

Here's the blog post being created

 

 

Here it is in SharePoint

 

Benefit: Permanent and Searchable

 

 

Here is the Email Notification

 

Benefit: still arrives as a real time email. I.e. the old school way this content would have been disseminated

 

 
Posted by Sean Wallbridge on 25-Jul-09
Bookmark this post with:        
 

Comments


Steve commented on Friday, 24-Jul-2009
Great post Sean. Understanding how to set up and use a SharePoint blog was one of things I placed on the back burner ... until now. You summed up things nicely. Question: Is it possible for me to subscribe to an article’s comment thread? That would allow one to receive notifications when new comments are added. To me that’s an important feature that I see missing in lots of blogs. When I post a comment and am interested in following the dialog I don’t want to have to keep going back to the article to see if there are additional comments. I recently added that feature to my Wordpress blog. Commenters can simply click a checkbox to “Notify me of followup comments via e-mail”. Anything like that with a SharePoint blog? Cheers, Steve


Sean Wallbridge commented on Friday, 24-Jul-2009
Sure you can, either by creating an alert on the comments or create a workflow using SharePoint Designer.


Steve commented on Friday, 24-Jul-2009
Hey Sean. Maybe missing something obvious here but where do I create an alert for the comments when I'm looking at the posting?


Sean Wallbridge commented on Friday, 24-Jul-2009
Hey Steve, In your Blog site, there is a list called 'Comments'. Choose 'View all site content'. It's a list like all the others. From there, you can choose to receive alerts (or choose it in SPD for your workflows).


Nick Hadlee commented on Saturday, 25-Jul-2009
Hi Sean, I just wanted to say I really like your idea and am pretty keen to set something similar up for our inhouse KB - we are still guilty of the email = loss of knowledge problem. What were the motivations for using a SharePoint blog site vs. other SharePoint methods of creating a KB? (Other alternative I'm sort of thinking of is that fantastic 40 KB wiki templates)? Based on your article the things that jump to mind for me is a.) Better interaction/collaboration via comments functionalty and b.) Word 2007 as the editor must provide a easy way to get information into the system quickly. Cheers Nick


Sean Wallbridge commented on Sunday, 26-Jul-2009
Hey Nick, I'm not sure how original my idea is, as it really is just using the core functionality of the blog concept and adding the reliance on educating our team to use it and subscribing to alerts within the team. But so far, it is proving pretty effective, for us anyways. We've got a KB as well, using the 40 Fantastic template as a base and the reason I've abandoned that is that it always ended up being 'too much work' for the authors (me and my staff) as by the time you opened up Word, put your thoughts together and finished the doc, you still had the task of 'filing' it somewhere). Plus, to review new articles, we were always opening Word, etc. as the 'viewer'. I like the idea of the HTML blog posts (created in Word) as it is instaneous viewing of content, searchable in SharePoint (ya, Word is searchable but you still need to open the doc, etc.) and because the 'authoring' process is so quick and easy, the team is more inclined to post, even if it is something tiny and seemingly insignificant - all those little nuggets build our internal knowledge base - quickly. We're more inclined to 'perfect' our KB articles, when they are focused on the article. We do encourage that the team use the 'comments' when commenting as their inclination is to reply to the alert email (that contains the blog post/content), which means those additional nuggets get lost in sent items - but I think I've curbed that with a few reminder messages.


Jeremy THake commented on Monday, 27-Jul-2009
This is a great walk thru. One thing I would point out is typically these KBs internally at our company trigger mass discussion. Commenting in Blog Posts is pretty limited out of the box and Wiki's are no better. Have you seen this issue?


Sean Wallbridge commented on Monday, 27-Jul-2009
Hey Jeremy. Good point. Though I suppose I'd argue that the benefit of having to manage internal comment, is that at least folks are talking (and sharing). Off the top of my head (and we use this on a 5 person team, so obviously I can't speak to large scale experience with this solution), would be to either create some workflows that handle the 'redistribution' of blog posts and/or comments (instead of plain alerts). Considering the comments list is yet another list you can manage/control, it just needs some creative energy in regards to how much/how you notify I suppose. I'll give it some thought, maybe there is more to add here (he says also realizing it is summer and we have a pool in the backyard that my 5 and 7 year old want me there with them :)

blog comments powered by Disqus