• Save
Using DITA-wiki Hybrid Solutions For Better Knowledge Systems
Upcoming SlideShare
Loading in...5

Using DITA-wiki Hybrid Solutions For Better Knowledge Systems



Want to reap the benefits of community-based documentation? This game-changing trend is gaining traction fast, but many organizations lack resources to build solutions. The open source DITA2Wiki ...

Want to reap the benefits of community-based documentation? This game-changing trend is gaining traction fast, but many organizations lack resources to build solutions. The open source DITA2Wiki Project is a free resource to do just that. You can get a proof-of-concept system up and running in an hour. A governing concept is mixing company-generated ("warranted") content with community-generated ("non-warranted") content to provide richer user assistance. And with DITA XML in the mix, you can deliver rich information online, offline, and directly within your apps.



Total Views
Views on SlideShare
Embed Views



2 Embeds 4

http://www.slideshare.net 3
http://www.linkedin.com 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • What turns non-warranted content into warranted content? It’s the age-old SME review process, adapted to latest technologies.
  • Get immediate updates using space/page watches and daily summaries.Let the community know that their contributions are being consumed.If you can write an email, you can write a wiki article – gentle prodding generates more content. Be an activist, be a librarian.Deliver special value that is not necessarily in other outputs.Info Dev owns the entire system. Some web developer skills are required, so proper staffing is important to the success of the system.
  • 1st report: What time zones are community members in? Helps determine SLAs for downtime alerts.2nd report: What screen resolutions should we focus web development efforts on? We were surprised to learn that we had incorrectly assumed smaller resolutions. This data created cost savings in development and testing.3rd report: Site overlay. Which navigation aids are getting traction? Where’s the best place to put that link? What’s not being used? Reclaim that real-estate for something different. Set a goal to refresh the GUI at regular intervals (e.g. every 9 weeks). Track the effect.Note: The sample reports do not reflect live system data.

Using DITA-wiki Hybrid Solutions For Better Knowledge Systems Using DITA-wiki Hybrid Solutions For Better Knowledge Systems Presentation Transcript

  • The open source DITA2Wiki Project
    Building DITA-wiki hybrids to reap the benefits of community-based documentation
  • What is the DITA2Wiki model?
    A framework for collaborative information development.
    Documentation source in DITA, output to wiki.
    Applies concept of warranted and non-warranted content. Different expectations, different interactions, integrated user experience.
  • Business goals
    Help customers and partners scale faster, better
    Increase everyone’s productivity
  • Use cases
    Find out what's new*
    Search for specific information*
    Share knowledge*
    Get notified of updates*
    Call out nuggets of information (e.g. rate, vote, favorites)
    Find something to play with
    Personalize the experience
    Ask a question
    Rant and/or rave
    Report a problem
    Talk about myself
    * Identified as highest priority
  • “Zoomquilt” 2 – Created by a dozen artists collaborating online
  • Brokered collaboration model for warranted information
    Cohesive collaboration model for non-warranted information
    Core contributors versus trusted contributors
    Reference: MIT Sloan Management Review, Fall 2007, Vol. 29: “Breakthroughs and the ‘Long Tail of Innovation’”; L. Fleming
  • “warranted”
  • It’s the age-old process…
  • …in which some activities are new
    Refresh (wiki)
    Publishing (all outputs)
    Update wiki
    Accept or reject contribution
    Run DITA2wiki in test
    Build release candidates
    Delete/archive old comments
    Receive notification
    Run DITA2wiki in production
    Inspect against wiki content
    Inspect incoming/outgoing links
    Acknowledge contribution
    Ship it
    Initiate updates
    Update done
  • “There will be a DITA-enabled wiki in the marketplace in 6 months.”
    Lisa Dyer, April 2005
  • System demo
  • The importance of reporting
  • Process brainteasers
    The trouble with comments
    As they collect on a page, info is harder to consume
    Comments have a life cycle, but how exactly do you define?
    Deleting comments might impact aspects of community equity
    What’s the best way to arbitrate community edits back into the source, in this case, DITA?
    Short answer: it’s the process, not the technology. Avoid over-engineering things.
    Content lifecycle
    Restricting views or edits: when is it an anti-pattern?
    Workflow: to automate or not to automate?
  • Architecture brainteasers
    Access point (hub space)
    Deliverable (= DITA map)
  • Thank you!
    Questions or feedback?
    DITA2Wiki Project home: http://sourceforge.net/projects/dita2wiki/
    DITA2Wiki Quick Start Datasheet
    Lombardi Blog: http://development.lombardi.com/
    Building a DITA2wiki hybrid: A new approach to reuse and personalized content
    White paper: Using Structured Wikis in Software Engineering
    Blueprint it. The easiest way to get started with BPM is now available!