FatWire is releasing the first fruit of the Infostoria wiki and blogging tool acquisition that it made barely six weeks ago. In essence, the new release rebrands the Infostoria tool as FatWire TeamUp, but it also adds one-click links so you can register wiki or blogging content in the FatWire content repository, or for repurpose content that was developed through FatWire content system as wiki or blog.

TeamUp’s core capabilities include a relatively simple means for non-technical users to set up blogs or Wikis, automatically generating emails inviting colleagues or partners to participate. It also enables you to convert blog or wiki content for deployment to mobile devices. It also has its own workflow capabilities, so that formal processes can be applied to setting up and managing blog or wiki content. It provides the requisite file transfer and caching, access control, indexing, tagging, and collaborative communications that you expect for developing and deploying content, except that this is content that has traditionally been considered much less formal.

Today, there is obviously a blinding array of choices when it comes to open source Wiki tools and hosting services – and of you click on sites like Wikimatrix, you can freely compare some of the tools that make your shortlist for commercial support, security features, CAPTCHA support, email and comments, tags, footnoting and other features.

Admittedly, Fatwire’s infostoria is not on the Wikimatrix list, but it claims that it is the first web content management provider to integrate blogs and wikis, or at least, enable you to repurpose content as blogs or wikis without having to move files or copy and paste. (Ironically, Wkimatrix is a free website established by Cosmocode, a Berlin, Germany-based integrate of web content management systems.

The integration, which consists of dedicated two way interfaces, is obviously a first step. While it makes sense in the grander scheme of things to classify Wikis and blogs as just another form or another face of enterprise web content, the fact is that you don't stifle the process by adding so much administrative overhead. You are, in essence, trying in some way to bridge the gap between formal and informal (or less formal) content. Consequently, for now TeamUp retains a separate, presumably lighter weight approval workflow than does FatWire’s core content system.

So obviously, the company will test the waters with its client base. It's clear that as blogs and wikis grow more mainstream, its customers will want to eliminate the silo that sets them apart from formal content. Consequently, while the press release touts the product roadmap for integrating the new offering, in actuality FatWire and its customer must still feel around to see just what the right level of integration will be.

---