Your SlideShare is downloading. ×
0
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Why DITA?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Why DITA?

510

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
510
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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.
  • Transcript

    • 1. Adopting DITA<br />Leaping Across the Chasm<br />Mathew Varghese<br />Content Architect, Citrix<br />
    • 2. Agenda<br />Why DITA<br />Basics of DITA architecture<br />Content reuse with DITA<br />Semantic tagging and topic-based writing<br />
    • 3. Why DITA<br />It’s all about adoptability<br />the chasm<br />
    • 4. 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 />
    • 5. Can your product sell itself?<br />
    • 6. Knowledge Stack<br />Interfaces<br />People<br />Product<br />Portals<br />Processes and Tools<br />People<br />Content Developers<br />Subject Matter Experts<br />
    • 7. DITA Building Blocks<br />Topics<br />Concept<br />Task<br />Reference<br />Maps<br />Ditamap<br />Bookmap<br />
    • 8. Core Reuse Features (1.1)<br />Ditamap<br />Ditaval<br />Conref<br />
    • 9. Ditamap<br />Topic-level reuse<br />C<br />C<br />R<br />T<br />R<br />T<br />C<br />T<br />T<br />T<br />T<br />
    • 10. DITAVAL<br />Topic-level reuse<br />Attribute<br />Element<br />Content<br />
    • 11. Conref<br />Element-level reuse<br />Conref<br />Element<br />Topic and location<br />Element ID<br />Topic ID<br />
    • 12. Reuse Scenarios<br />Across releases<br />Across deliverables<br />Guides<br />Formats<br />Across audiences<br />Across functions<br />
    • 13. 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 />
    • 14. 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 />
    • 15. Semantic Tagging<br />Build your tagging scheme<br />
    • 16. Analysis and Design<br />Design Walkthroughs<br />Topic Audits<br />
    • 17. Tagging and Editing<br />Editors are your greatest assets!<br />
    • 18. QUestions<br />

    ×