why dita?
DESCRIPTION
TRANSCRIPT
Adopting DITA
Mathew VargheseContent Architect, Citrix
Leaping Across the Chasm
Agenda
• Why DITA• Basics of DITA architecture• Content reuse with DITA• Semantic tagging and topic-based writing
Why DITA
It’s all about adoptability
the chasm
Think Information not Content
“Come at once. We have struck a berg.”
Content
KnowledgeContent is a symptom, not a solution!
Can your product sell itself?
Knowledge Stack
Interfaces
Processes and Tools
People
People Product Portals
Content Developers
Subject Matter Experts
DITA Building Blocks
TopicsConceptTaskReference
MapsDitamapBookmap
Core Reuse Features (1.1)
Conref
Ditamap
Ditaval
Ditamap
C
C
RT
TT T
Topic-level reuse
C
RT
T
DITAVAL
Topic-level reuse
Element Attribute Content
Conref
Element-level reuse
Element Conref Topic and location
Topic ID
Element ID
Reuse Scenarios
• Across releases• Across deliverables–Guides–Formats
• Across audiences• Across functions
Semantic Tagging and Topic-based Writing
• Get the specs• Develop your tagging scheme• Strengthen your analysis and design process• Tagging and editing
Get the Right Specs
• Language Specification• http://docs.oasis-open.org/dita/v1.1/langspec
/ditaref-type.html
• Architecture Specification• http://docs.oasis-open.org/dita/v1.1/archspec
/archspec.html
Semantic Tagging
Build your
tagging scheme
Analysis and Design
Design Walkthroughs
Topic Audits
Tagging and Editing
Editors are your greatest assets!
QUESTIONS