1 / 58

Product Content Evolution The Structured Phase

Product Content Maturity Model Series. Product Content Evolution The Structured Phase. Agenda. Introductions Product Content Maturity Model Overview The Autodesk Story SDL Trisoft. Our Presenters. Andrew J. Thomas Director, Product Marketing SDL. Marie Salet Principal CMS Engineer

nalani
Download Presentation

Product Content Evolution The Structured Phase

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Product Content Maturity Model Series Product Content Evolution The Structured Phase

  2. Agenda • Introductions • Product Content Maturity Model Overview • The Autodesk Story • SDL Trisoft

  3. Our Presenters Andrew J. Thomas Director, Product Marketing SDL Marie Salet Principal CMS Engineer Autodesk

  4. Product Content Maturity Model Overview

  5. Current Pressures

  6. The Engaged Vision • Deliver Product Content on demand • Content created and filtered for Customer Profiles • Interactive and dynamic, while still versioned and controlled • Incremental Updates • Analytics beyond page hits to capture “content utility” • Enable social interactions between community and authors • Crowd Authoring through easy WYSIWYG interface • Branding and terminology maintained, regardless of who creates the content • Content re-used consistently at every creation point

  7. Product Content Marketing Engineering Product Content Training & Learning Partners Field ServicePersonnel Support

  8. Product Content Maturity Model

  9. Phase 2: Structured • Company Overview • Investment in structure has begun and older unstructured content is being migrated into DITA • New writing tools are being deployed and content creators are focused on learning new creation methods • Best Practices • Choose team evangelists that can help others with learning curve issues • Deploy a component content management system during migration to increase operational efficiency • Develop a content re-use/sharing methodology • Allow new roles to emerge – information architect, shared content lead • Next Steps • Finish conversion of legacy documents • Reach out to other departments involved in product content to determine what content can be re-used across

  10. Content locked in context Information can’t easily appear in multiple context and can’t be tailored readily to audience High costs of formatting Content gets out of synch and is difficult to refresh Customers can’t find what they need XML Topic Methodology Content can be reshuffled for deliverable Same content can live in multiple outputs Content can be delivered easily as web pages to consume Metadata and conditions can allow content to be tailored on the fly Content can be easily refreshed Benefits of DITA Traditional Book Methodology Topic Based / DITA Methodology

  11. Contracting Product Life Cycles English Release International Release PRD Shelf Life Traditional Research & Development Author Review Publish Localization Market Life Research & Development Modular writing Global Revenue & Market Capture Life Author Review Publish Localize Key:

  12. The Autodesk Story: The Road to DITA Marie Salet Principal CMS Engineer

  13. The Road To DITA • About Autodesk • Deciding to Move • Unstructured to Structured • Structured to DITA • Lessons

  14. Autodesk Autodesk is a world leader in 3D design, engineering, and entertainment software. The broadest and deepest product portfolio in the design world 10 million+ users in over 800,000 companies 3,500 development partners 1.2 million students trained on our products every year 6,800 Employees in 95 Locations Founded 1982 Fiscal year 2011 revenue US$1.95 billion

  15. Product Documentation at Autodesk • Our products are complex and require extensive documentation • Autodesk documentation regularly wins awards • Product documentation localized into up to 19 languages • High volume of source content (12 million words) • Technical writing groups decentralized • Localization is a (mostly) centralized organization

  16. Show and Tell

  17. Even for the web

  18. Once upon a time, a long long time ago…

  19. Documentation Localization • Decentralized Tech Pubs departments created documentation in many formats: • RoboHELP • HTML, created in Dreamweaver, HomeSite, NotePad • Unstructured FrameMaker converted to HTML using WebWorks • Proprietary tools • Localization challenges included: • Managing manual handoffs between writers and translators • Investing heavily in Tech Pubs engineering to handle diverse formats, technical challenges • Spending substantial $$ for desktop publishing

  20. Getting Our Feet Wet

  21. Localization Proposes Buying a TMS/CMSGOAL: Reduce localization costs and improve efficiency • Winter 2003: Start of pilot project • Spring 2004: Pilot project completed • Fall 2004: First major product releases in WorldServer • Spring 2005: First WS cycle completed for all major products

  22. Migrating Content to Structured • Migrating unstructured content to XML was not a trivial effort • Automated scripts and programs were developed to migrate content, but… • Extensive manual cleanup was required after content was in XML. Writers needed to do much of cleanup because they were the ones who knew the content.

  23. Developed the CPM Data Model • Developed the CPM (Common Pubs Model), a corporate-standard XML model for technical publications in 2002/03 • Supports specialization of a base element set, and makes use of the class attribute value to define specialization inheritance • CPM specialization is "additive" rather than "restrictive", however, which is more flexible but precludes content sharing via "generalization" • Can share content authored using the "base" model amongst specializations however, as is done for the I&L books • Single-sourcing managed via XML attributes (e.g. product-exclude, product-include, units, mediaExclusions)

  24. Getting Support…and Facing Resistance • Authoring Tech Pubs teams could not agree on a single data model (DTD) • Teams had to invest time and money to convert unstructured docs to XML format • Authoring teams had to learn structured authoring and drastically change way of working

  25. Success

  26. Success • We can output HTML or PDF from any of our source with the click of a button or on a scheduled basis • Documentation localization costs go down on projects year over year • Throughput has increased dramatically • Translation memories are managed centrally and are very high quality • Localization workflow is highly automated

  27. Help and PDF Automation XSLT XSL-FO PDF HTML XMLrepository

  28. Never Satisfied

  29. Challenge Create an environment that provided better performance and stability for our authors. Provide better authoring tools which will enable them to focus on content development rather than fighting with the tools. Resulting in faster time to market.

  30. Separate CMS and TMS • WorldServer is a TMS not a true CMS • Versioning • Link Management • Assembly

  31. Custom DTD or DITA Supporting a custom DTD • Authoring tools • Rendering • CMS DITA • Industry Standard • Out of the Box Tools

  32. Déjà vu

  33. Trisoft • Component Content Management System • Versioning • Workflows

  34. XMetal • Integrated with Trisoft • DITA

  35. Customizations Importer Set Metadata Publishing Environment World Server/Trisoft integration Autodesk Branding

  36. Support and Training • SharePoint blogs • Yammer • Train the trainers

  37. Lessons Learned • Get an Executive sponsor • Manage change • Don’t do everything at once • Ensure a front to back strategy (including localization) • Set expectations • Communicate!

  38. The Eco System

  39. The CMS Ecosystem Web-Based Help (WBH) or HTML Help Autodesk User Assistance Content Content CMS SDL Trisoft *Any* Autodesk Content Translation CMS SDL Worldserver+ TMs LS Translation Ecosystem Machine Translation (LS-trained or LS-supported) Community Content Translators’ Review & Post-editing

  40. Marie.Salet@autodesk.com

  41. SDL Trisoft

  42. Structured Product Content Suite Global Customer Engagement Intelligent Product Content Dynamic Delivery Reviewers / SMEs / Casual Contributors Structured Content Infrastructure Component Content Management DITA Content Quality Checking

  43. Most companies adopting component content management (CCM) • Content Management Focus to Handle XML “Component Content Management” • Vision of single CMS for every business maturing to specialized systems • Web CMS , Source Control, Component Content all driving specializations • CMS’s that are not developed to specialize with DITA can’t meet requirements • Companies with standard CMS’s are adopting CCM to handle DITA (Dell, VMware, Nokia, + others)

  44. Increase Productivity

  45. The Problem of DITA Management

  46. DITA Plus Translation

  47. Differences of CMS and Component Content Management

  48. Publication Object Electronic output format • Publication Object=> output • Master Document (e.g. DITA Maps)=> assemblage/ structure • Components(e.g. Topics, illustrations...)=> content Layout template Baseline Context Variable definition

  49. Baselines Secondedition Thirdedition Firstedition t Versions

More Related