FatWire recently announced the release of two new products -Gadget Server and Community server. These social computing products are tied directly to FatWire’s Content Server (CS), a Web Experience Management (WEM) platform.
Yes, there are not enough gadgets for content contributors and community server does not offer anything more than just blog functionality, but I think the idea behind is to “populate” or “pull” content from the end users. A young platform laid out for a two-way content collaboration i.e. exchange of content from both corporate content contributors and site visitors.
Having said that, this is my take on the recent release –
1. WCM Implementation in Conjunction with Portal:
Customers with existing Implementation of FatWire Spark-pCM on Sun/Weblogic portals have a luxury of using various portlets which are tightly integrated with CS. Administrators could easily configure portlets based on editor’s needs. So, in this scenario just a few WCM specific gadgets will not make much of a difference for editors, but developers can easily place these gadgets on any web page as a part of FatWire page layout process.
Personalization is a capability that every portal offers, based on requirements, personalization at multi levels can be configured using portal itself. Additional Investment on gadget server will not be much beneficial unless you have a requirement to let template developers utilize the capabilities to add gadgets on web pages during page layout process or for the end users to personalize their dashboards with these light-weighted apps. The usage of gadgets become positive within the WEM framework where Site Admin wants to create a page with certain layout and include these gadgets within the slots. It’s a quick and easy way of developing new content-centric pages. Another advantage is gadgets created within FatWire’s Gadget Server can be exported for use on third party websites such as igoogle.
2. Pure WCM implementation for external WebSites:
It really depends on what type of website one has. For a website selling products online, it will be a nice idea to implement functionalities offered by Community server as it will get you customer’s feedback and reviews related to product sold. This can potentially be a platform for you to support customers online, share best practices or share product manuals. As good it may seem from the user end, it is equally difficult from the website management perspective. Most of the user generated content will be stored in the Production environment while Staging will just be used by internal content editors. Different information will be stored in various silos and IT will have to work around syncing of content between environments.
3. Pure WCM implementation for internal Sites/Microsites:
I see a huge potential in this area. We have a large number of ‘social networking’ platforms and tools in the market and over internet. What lags in the WCM space are the tools and functionalities by which internal users within an enterprise can be networked together and form a ‘content collaboration’ space.
With community and gadget server integrated within the WEM framework, the realm of WCM is extended, so does the flexibility of retrieving and contribution of information from the internal users. If wisely implemented and keeping security and authorization into consideration, information and knowledge can be reused, relevant content can be collaborated from across the boundaries and from within a business unit of your enterprise. Now, it’s on the individual organization’s WCM strategy how they drive productivity around information. All an all a right Content Strategy that clearly identifies the demarcations and overlap of document, social and content collaboration.
Most of the organizations believe in ‘push’ of the content. The push of content happens at various levels, it can be targeted to either one business unit of the organization, or to a partner on extranet, or to the site visitors on internet.
There are valid use cases and business requirements for the same, but that’s not the point where the story ends. Enterprises today are not just targeting content (newsletters, campaigns, product info, recommendations etc) to the end user but emphasis is being given to ‘pull’ of information from the end user. There is a need of a business channel that is interactive. This 2-way methodology of content contribution and collaboration helps organizations to–
1- Create a Knowledge repository from the users of a particular business unit working towards a similar goal.
2- Get actual feedback from the site visitors
3- Interactive Support
and most importantly -
4- Reach out for useful insights
Rich back-end content management systems with complex features are around for a while. A non technical business user finds it difficult to learn, contribute and manage the content.
WCM products lag User Experience, which is quite seriously taken up by collaboration products. Amalgamations of these two categories of product are on the roll and the adoption will be fairly wide in the near future.