All the knowledge that the user needs to adopt the product should provided as efficiently as possible.
We want to harness the knowledge that people within the organization possess. Content doesn't’t isn't a true representation of our products.It’s time to pull the experts.Documentation lacks depth – shows that somethings wrong in the knowledge sharing area.Creating lots of content is not the solution, We need to find a smarter way of pleasing the customer.
This diagram illustrates the components of a knowledge ecosystem. The size of each component indicates the relative impact each component has on the efficiency of the ecosystem.
Adopting DITA<br />Leaping Across the Chasm<br />Mathew Varghese<br />Content Architect, Citrix<br />
Agenda<br />Why DITA<br />Basics of DITA architecture<br />Content reuse with DITA<br />Semantic tagging and topic-based writing<br />
Why DITA<br />It’s all about adoptability<br />the chasm<br />
Think Information not Content<br />“Come at once. We have struck a berg.”<br />Content<br />Content is a symptom, not a solution!<br />Knowledge<br />
Semantic Tagging and Topic-based Writing<br />Get the specs<br />Develop your tagging scheme<br />Strengthen your analysis and design process<br />Tagging and editing<br />
Get the Right Specs<br />Language Specification<br />http://docs.oasis-open.org/dita/v1.1/langspec/ditaref-type.html<br />Architecture Specification<br />http://docs.oasis-open.org/dita/v1.1/archspec/archspec.html<br />
Semantic Tagging<br />Build your tagging scheme<br />
Analysis and Design<br />Design Walkthroughs<br />Topic Audits<br />
Tagging and Editing<br />Editors are your greatest assets!<br />