Browser and wiki workflow independence with Liferay the open source “SharePoint”

July 4th, 2009; today is the US independence day. This has put me in a reflective mood. As I was thinking about the current projects that I’m working on, I thought about this…


SharePoint 2007 is a great improvement over its ancestors: SharePoint 2003 and SharePoint 2001. The capabilities in document management make the old shared file systems obsolete. This is especially true for Microsoft Office products that integrate with SharePoint. I’m waiting for SharePoint 2010 to hopefully resolve some of the issues that the blog and wiki tools have. In the meantime, we have wiki and blog requirements that need to be met. In our search for a top flight wiki that was easy to learn and use by users; we discovered Liferay.

    Actually we rediscovered it :-). I had looked at Liferay in August 2008, to establish a community for another company; however they decided, that they could not provide the resources to host an “active” community. Part of providing a community is the nurturing and feeding of the community by providing content on a “regular” basis and responding to comments.

From 100,000 feet, Liferay is essentially an open source version of SharePoint written in Java. Liferay embraces document collaboration, Web 2.0 and social collaboration. A Liferay portal provides one or more organizations with one or more communities. Each community and user has public and private pages. Users can be assigned roles within multiple organizations and communities. Liferay plugins, portlets, can be added to any page by any user based on their “scoped” role. Liferay themes and layouts can be established at the community level or applied to each page.

Liferay provides wiki and blogging editors that can be configured to support either the FCKeditor or TinyMCE. This allows users that are already familiar with other Social media tools to be immediately productive. One of our litmus tests for wiki and blog usability is: can a user “easily” learn to how create an attractive blog or wiki that is media and content rich without having to result to editing raw HTML? This should be possible without formal training. Yeah, I expect the user would read some documentation and view some training videos; however, since more and more users are using social media sites, they are looking for their corporate tools to resemble their other tools. The workflow in these tools should allow the user to work top-down as they are thinking. Although not perfect, we find that Liferay passes this test.

    One of the disruptive behaviors of internet-based systems and web 2.0 is that corporate systems and vendor applications lag many internet applications in technological advances. This means that users are often waiting for the applications that they use at work to catch up with the ones they use personally.

Liferay allows the use of existing content or the dynamic upload of content while you are are writing. SharePoint 2007 only supports use of previously stored content while editing.

    Okay, I know that you can open another browser window; upload some content; and then switch back to your wiki/blog window to complete the wiki or blog entry. However you cannot imagine how many users do not think of this or understand this. I been around long enough to realize that means that there is likely a disconnect between the user’s desired workflow and the product workflow.

The Liferay wiki and blog editors work equally as well with Internet Explorer,IE, and FireFox. SharePoint 2007 provides a more robust experience to IE users. With SharePoint, in my opinion, wiki and blog editing in FireFox feels like an “unwanted disease”. This is unfortunate. There are standard JavaScript libraries that abstract browser dependencies. There is simply no technical reason that SharePoint can’t provide a first class experience to most browsers. The Liferay content portlet can contain javascript, this allows easy integration with a plethora of other social media and web-based applications. Ironically, I placed my Windows Live status with a button into a Liferay content portlet and it behaves correctly. I could not do this with SharePoint. The SharePoint editors deleted the javascript code. The Liferay Wiki can be configured to support Creole or Camel-case wiki editing.

You know, SharePoint could learn a lot from Liferay.

Be Sociable, Share!
This entry was posted in JAVA, liferay, SharePoint and tagged , , , . Bookmark the permalink.