Author

• Tony Byrne, mailto:[email protected]
• IDEV http://www.idev.com

Agenda

• Overview: Trends Good and Bad
• CM Spectrum
• Product Categories & Comparisons
• Avoiding CM Pitfalls
• Q&A

Not Covered

• CM Evangelion
• Juicy Gossip
• Mandating Pick
• "Higher math" pricing

Overview

Bad Trends

• Immature space
• Confusing array
• Rapid evolution
• M&A
• Caveat emptor

Good Trends

• "Pure-play" CM and older DM/AM products converging (no KM yet)
• E-commerce savvy -- if you want it
• Clearer choices w/ specialization
• Larger installed bases
• Some ASP models emerging

CM Spectrum

Three Phases

1. Production
2. Publishing
3. Distribution

some overlap: index/search, promotion/caching, etc.

Role Management

• Who is allowed to do what (and when)?
• Level of granularity?
• Authentication mechanism?

Authoring & Transformation

• How stuff gets into CMS
• Accessing the System: browser vs. client
• Forms-based entry & knowledge of HTML
• Document conversion
• Content validation & link validations
• Leverages XML?

Aggregation

• Dealing w/ mutliple content repositories / data types
• Importing syndicated content
• Intra-enterprise vs. Inter-enterprise CM

Tagging

• Assigning Metadata
• Custom vs. limited tag sets
• Who and what has access to metadata

Editing & Approval

• Sometimes "workflow"
• Rules flexibility
• Branching vs. Linear
• Modeling mechanism?
• Triggers?
• Process reporting?

Versioning

• Site Versions and "editions"
• Roll-back? How far? What elements?
• Date- and time-award publishing
• Version control: check-in/out
• Linear vs. branching VC

Indexing & Searching

• Bundled vs b-of-b
• Fielded vs full-text
• Needs internal search, anyway

Page Generation

• File system vs dynamic generation (and combos)
• Template flexibility; component granularity
• Design and layout limitations?
• Database dependencies
• Incorporate logic from other subsystems?
• Speed...

Customization & Personalization

• C vs P?
• Bundled vs b-of-b
• Personalization models
• Admin tools
• P expensive both at design and runtime.

Content Promotion

• Dev -> Stage -> Production
• Code promotion as well
• Separate from editorial workflow

Caching

• Importang perf. issue even for low-traffic sites
• Rules-based? Level of control?
• File vs. Page vs. Object caching

Clustering

• Oops

Wireless & Other Formats

• Dis-aggregating
• WAP/WML may not be hard; tools are nice
• PDF, Word, other formats?
• Print-enabling Web publishing

Syndication and CDSP Networks

• CDSP is Akami acronym: Content Distro Service Prov
• Standards adherence: WebDAV, ICE, XML
• APIs for major syndicators
• "Edge Networks": Akamai, et al

Checklist

• E-commerce tie-in
• Other partners
• OS / DBMS

Major Full-Spectrum Players

• Tend to be newer, Web-centric products
• Six-figure licensing
• Platform-orientation
• Reinventing as e-commerce plays
• What you get:
  • scaling
  • reusable comp arch
  • modular
  • Java (usually)
• Vignette V/5 Platform
  • Multiple servers to complete spectrum
  • Loved and reviled
  • 35-45% service revenues
• Xpedio (IntraNetWare)
  • Content Server vs Content Publisher
  • Extensive XML
• Spectra (Allaire)
  • Methodology mandated
  • "low-end", broader vs. deeper
  • "Excel" chartish UI
• Content Server (OpenMarket)
  • formerly FutureTense
  • "lowest highest" Forrester ranking
  • Broad array of features, straightforward
• Expressroom I/O (WorldWeb, Starbase)
  • Pure Java/XML
  • Future suspect?
  • Code vs. content managment

Production Oriented Products

• TeamSite (Interwoven)
  • Partner with app server vendors to deliver content
  • "Sandbox" model
  • one piece well
  • performance?
• Engenda (EPT)
  • Pure workflow
  • Very open architecture
  • OODBMS

Established AM/DM Products

• Documentum
  • "Compliance" editions
  • Some attack on inter-enterprise issues
• Insight/3C (Enigma)
  • NT proprietary client
  • Focused on extranet/B2B
  • "CommunitySite" for customer participation
• Content@XML (XyVision)
  • Proprietary clients
  • Suited to reference publishers, strong ML bg

Other Alternatives

• German Invasion: Gauss, Imperia
• OS Solutions: Zope, Midgard, Mason
• Very low cost: openshare, Ektron, Frontier, Egrail
• Do-it-yourself still valid option?
• Ektron WYSIWIG component

Common Pitfalls

• Confusing CM Packages w/ CM Systems
• Limiting business case justification to ROI; CDB may be more apt.
• Not spending enough effort organizing / describing content.
• Picking CMP in advance of solid reqmts
• Picking CMP which won't play well with others
• Underestimating HW & ongoing tech support needs
• Understimating integration & service needs (license may be 1/2 to 1/3)
• Missing / sluffing internal change-managment issues
• Others?

Future of CMPs

• Niche offerings & consolidation
• Clearer lines among:
  • Enterprise
  • Mid-market
  • Lower-end
• Java / XML gravity
• Enhanced inter-enterprise functionality
• Many choices