250 likes | 367 Views
CMS and Portals | How do they really work?. IA Summit, Las Vegas | March 24, 2007. Tony Byrne & Theresa Regli tbyrne@cmswatch.com tregli@cmswatch.com. Independent evaluations of content technologies & practices. About CMS Watch. The Web CMS Report evaluates 30 Web CMS packages.
E N D
CMS and Portals | How do they really work? IA Summit, Las Vegas | March 24, 2007 Tony Byrne & Theresa Regli tbyrne@cmswatch.com tregli@cmswatch.com
Independent evaluations of content technologies & practices • About CMS Watch The Web CMS Report evaluates 30 Web CMS packages. Enterprise Search Report evaluates 28 Search vendors. • Coming soon: • The ECM Suites Report • Web Analytics Report • Portal Project Starter Kit Enterprise Portals Report evaluates 15 major Enterprise Portals vendors.
Agenda • Fundamental differences between Web CMS and Portal • Looking at systems based on personas, business scenarios, usability • Typical surprises IAs encounter about how the technology works on the "back end" • Best practices for how IAs can effectively impact CMS and Portal implementations
Industry-leading, scalable solution for the enterprise, fully customizable for your needs, with robust API, Web Services support, and lowest TCO in its class, blah, blah, blah… How does it work? How much does it really cost? What’s wrong with it? Who are their real competitors? Do their consultants know my industry? Will my co-workers actually use it? “Markets are Conversations” -- Cluetrain Manifesto • About CMS Watch
What does a portal do? • Layers of Services
What does a portal look like? • Layers of Services
CMS Portal software What do you get in a portal vs. a CMS? Categorization Acquisition Management Composition Delivery web Internet, Intranet, Extranet medias SMS, WAP, 3G, PDA automatic/ manual categorization browser text, images, video email word processors Word, Notes object management editing, revision tracking, workflow, versioning creating the user experience print PDF, Quark XPress feed Reuter, AFP, AP, RSS syndication web feeds (RSS) search enterprise systems ERP, CRM, legacy, Quark Xpress email alerts, newsletters taxonomy import tool importing existing sites ?
Agenda • Fundamental differences between Web CMS and Portal • Looking at systems based on personas, business scenarios, usability • Importance of scenarios • The usability conundrum • Typical surprises IAs encounter about how the technology works on the "back end" • Implications for content modeling, navigation, and design • Best practices for how IAs can effectively impact CMS and Portal implementations
Usability: CMS vs. Portal / Situational vs. Canonical OR "People designing applications are looking for rules, but practitioners know that it is situational: you could install the right widget, but if it's not prominent enough, it won't work." -- Steve Krug “The Canonical Intranet Homepage” -- source: useit.com
Understanding Needs | Scenarios and Personas for the “Back End” • Tell a (testable) Story The larger the group, the simpler the tool…
Portal Usability? Very dashboard-oriented • Products > MOSS 2007
Agenda • Fundamental differences between Web CMS and Portal • Looking at systems based on personas, business scenarios, usability • Typical surprises IAs encounter about how the technology works on the "back end.” Implications for • Content modeling • Navigation • Design • Best practices for how IAs can effectively impact CMS and Portal implementations
What does all this mean for an IA? • It’s not just about the front end user experience! • Or at least: what you want on the front end has major implications on the back end. In other words… • Information architecture is like “the force” when it comes to implementing these technologies: the great unifier, what the systems need to bring content together and display it accurately • Many Web CM and Portal systems rely on solid metadata and classifications in order to be able to do *anything* • How you choose to model content in the repository, and how the system you choose leverages taxonomy, greatly influences the business value you can realize
Example | Analog Devices Consists of categories and sub-categories to classify complex semi-conductor products
Two Taxonomies Broadband Products • Product Taxonomy • Hierarchy of products • Leaf elements are products • Require at least one product • Content Taxonomy • Hierarchy of content types • Leaf elements are content types • Require at least one sub-type Broadband Amplifiers AD8320 AD8322 AD8324 Related Tech Info Technical Articles Application Notes EE Notes These are managed in separate repositories!
“Placeless” vs. “Placeful” content | Applying business logic Press Release Category-specific press release Product-specific press release
How content is modeled changes what the system can do Product and content taxos are linked via business logic, creating information suite around a single item. Content granularity is key in this scenario.
Content granularity enabling user experience • Category-specific content • Categories in taxonomy leveraged to dynamically create category-specific product listings • Content granularity enables product comparison
Broadband Amplifiers Related Tech Info Web Laws Broadband Amplifiers Bridge Laws Data Sheets Press Releases Data Sheets Press Releases AD8320 AD8321 AD8322 Content Types Metadata Logic Behind the Presentation • Taxonomies are made up of product and content types • Content items have a type and are tagged with products • This relationship is used to build pages ADI Announces New Product Content Item Press Releases AD8320 Content Types Metadata
Good “back-end” IAs can “think like a CMS” Content For: Query For: Related Tech Info Press Releases OR Data Sheets = (AD8320 OR AD8132 OR AD8122) AND (Press Releases OR Data Sheets) Broadband Amplifiers Related Tech Info = AD8320 Related Tech Info AD8320 AND (Press Releases OR Data Sheets) =
Best Practices for IAs • “Think like the system” • Know how the system and content model affects both the content contributor and content consumer. • Develop personas and scenarios for the “back end” – they’re not just for end-users of the web site • Think about the process implications of content analysis • Become a CMS/Portal user advocate • (If only because no one else will!) • Advocate for better application usability
Thank you! • Contact Info tbyrne@cmswatch.com tregli@cmswatch.com www.cmswatch.com