I had TeamPage running in under an hour on a Windows Server 2003 setup. There’s an optional plug-in for authentication using Active Directory, LDAP, or other systems simultaneously. Yet, even if you set up users manually, the polished Web administration speeds the job – along with other tasks, such as building sites. In the latter case, TeamPage’s default Front Page (dashboard) and workspaces should be more than adequate for most enterprises out-of-the-box.
Still, project administrators can easily configure the Front Page and project pages to display query-driven sections — along with changing pages to match corporate branding. For instance, I created several groups including project managers. Then, when a manager logs in, he or she would see a list of status reports and meeting notes. Conversely, team members’ main page displayed issues to address, questions requiring answers, and articles of interest.
I also liked the way TeamPage simplifies getting around. The navigation pane provides one-click access to different projects, sections (such as issues), and also let me sort by labels.
Another high point is how truly easy and quick it is to publish content and comments: Just click on an Add button and post using the Web-based WYSIWYG editor (e-mail, RSS syndication, or an Instant Publisher client are other content-creation options). File attachments are managed through WebDAV (check-out, lock, check-in, version control). When I hovered over a posting, an AJAX-style menu appeared that let me perform all sorts of actions, from editing and commenting to adding labels.
Traction 3.7 added a Wikipedia-style display for spotting differences between any two page versions. This really helps when a workgroup must edit and review articles. Further, a rich-text comment form let me quickly create threaded discussions on full articles or even specific paragraphs.
Beyond the system-generated filtered views, TeamPage has abundant ways that I used to manage content personally. To begin, Traction’s unique Collector let me group (bookmark) articles and comments for later recall or immediate action. Further, I inserted widgets within the text of articles; these objects create mashups of links and content from any Traction query, and they show text and graphics from any external source (perhaps a live weather report for any ZIP code). Traction ships with a live widget that recognized the text pattern of a UPS
Click for larger view. |
TeamPage’s many communication conduits worked effortlessly. I exported entries or content collections to Microsoft Word and PDF. RSS and Atom feeds are standard. Moreover, TeamPage will notify users of new content or comments through a Jabber instant message. An automated Executive Summary e-mail digest keeps each user informed of new postings. Yet what I found most useful was the Email Out function. It let me collect articles; compose a message in Traction; create a distribution list from Traction users, LDAP, or Active Directory; send the articles; and post the message to Traction.
Traction’s journaling system, mirroring
Click for larger view. |
After reviewing these four products, they clearly fit in different strata. All have the bedrock of usability and fast setup. What’s more, they work like the Web, so groups can share information and collaborate without much learning.
Socialtext, then Near-Time, offer wiki collaboration, team Weblog publishing, search, simple file management, and some personalization. Atlassian Confluence moves up a layer with better content organization and extensibility. Traction TeamPage clearly placed above the others with its superior ease of use and query ability that presented each user with just the knowledge they need.
Mike Heck is a contributing editor of the InfoWorld Test Center.
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Talkback
E-mail
Printer Friendly
Reprints




