Home > WSS Customisation > Custom Web Part Pages in WSS (Part 1)

Custom Web Part Pages in WSS (Part 1)

Okay, so WSS 3.0 doesn’t have the nice publishing features available with MOSS 2007.  However, there are a few things that we can do to improve upon the Web Part Page available out-of-the-box with WSS.

This series of posts will guide you through the process of creating a content type for an enhanced Web Part Page that can be versioned within a document library, searched using WSS Search and takes advantage of the Telerik RadEditor Lite content editor.


To place these posts within context, I’d recommend reading this blog article by Tuen Duynstee.  Tuen’s article was really my starting point for creating an internet-facing WSS 3.0 site.

Now to the fun stuff…

Problems with WSS Web Part Pages and the Content Editor Web Part

The most obvious way to provide users with a Web Content Management system using WSS is to drop the Content Editor Web Part onto a Web Part Page.

Unfortunately there are several serious issues with this approach:

  1. Content Editor Web Part content isn’t versioned.  You can create as many versions the web part page as you like, the actual content – which is contained within the Content Editor Web Part – isn’t versioned.  This is a wider problem with web parts in general, but especially of note when attempting to provide web content management.
  2. Content Editor Web Part content can’t be searched.  Yes, this is as bad as it seems.  Add your content to the Content Editor Web Part and it can’t be seen by the WSS Search.


There is another issue with the Content Editor Web Part; whenever you re-open the web part to update content it turns all server-relative URLs into absolute URLs.  Therefore if you have your content accessible from different addresses (when you have an extranet and an intranet for example) any linked content will be broken for one of them as soon as anyone updates the content.  The only way around this is to edit the HTML directly.  Hardly suitable for non-technical users.


In a nutshell: create a Content Type to contain the web content within the page itself and make use of the superior Telerik RadEditor Lite content editor.

Stay tuned for the step-by-step guide on how to do this in Part 2.

  1. Keith
    December 1, 2008 at 10:45 am

    Look forward for Part 2 solution!

  2. Larry
    December 6, 2008 at 5:41 am

    Great article. When is part 2 going to be posted?

  3. January 12, 2010 at 11:27 am

    Great Article !
    I have done something like that.
    If you would like to follow this idea, please let me know!

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: