On Nov 10, 2011 and again in 2012, Gartner released it’s annual “Magic Quadrant for Web Content Management“. As seen in the quadrant, Autonomy product stack is a clear leader. In this post we take each fundamental WCM feature that Gartner puts forth and discuss it from an Autonomy Product stack’s implementation perspective.
Gartner’s comments are in italics and bold. Read on, and feel free to provide your comments below.
Functions:The WCM offering must be available as a stand-alone product, or suite of products, and include the following capabilities:For a detailed view of Autonomy’s WCM product stack and it’s reference architecture, we recommend you read our previous blog post here
A content repository with basic library services, such as check-in/check-out and versioning.
TeamSite’s file-level (Submits to TeamSite STAGING) and site-level versioning (EDITIONS) are powerful features out of box. On top of this, the content services API provides command line and Java API for powerful integrations with other corporate applications as needed. This may not sound all that thrilling, but in an enterprise eco-system consisting of upstream and downstream applications feeding into your WCM system – these capabilities are very important.
Authentication of users (authors, editors and reviewers) and assignment of permissions.