Compared to PBwiki, Wetpaint offers a more compelling set of features if you can tolerate the ads that show up on your wiki. For starters, you can choose from a wider variety of functional and design templates to get your pages up and running quickly. PBwiki, on the other hand, only offers five skins for you to customize the look and feel of your pages.
In some ways, Wetpaint is more than just a wiki where people collaborate on a a set of documents. With features such as discussion groups and to-do lists, Wetpaint incorporates some functionality found in project management solutions such as Basecamp.
Other features present in Wetpaint that are missing in PBwiki include the ability to assign tags to individual pages. This is useful in promoting serendipitous browsing, especially for potential contributors who may want to get an overall idea of what a particular wiki is about by looking at the tags.
As an advertisement supported service, Wetpaint also includes features such as the ability to point your wiki to a custom domain and access to site statistics. Both features require an upgrade to a paid service in PBwiki. Technically, you could embed tracking code from third-party site trackers in your PBwiki, but without access to the CSS design templates which you'd have to pay for, you will not be able to effectively track site traffic as a whole.
Labels: library 2.0, scils598, wikis
Thank you for this review. I was looking for exactly this type of article, and fortunately for me, you've made it easy for me to choose between the two.
Thanks.
Drisnil said...
June 19, 2008 at 2:06 AM