Podcast — DITA: From the Perspective of Someone Actually Using It

Download MP3 (right-click, select Save As)
Duration: 42 min.

In this podcast, Marlene Martineau of New Dawn Technologies explains why they adopted DITA, how they adopted it, the benefits they’re experiencing, and the reasons why she’ll never go back.

If you’re unfamiliar with DITA, it’s a way of tagging your content so that the DITA Open Toolkit can transform it into a number of outputs, such as HTML and PDF. The tags conform to a specific XML architecture, and your information is chunked into small topics that can be arranged in different tables of contents (“maps”).

DITA is quickly becoming the XML standard for technical writers. New XML editing tools are sprouting up that allow you to more easily write DITA content without dealing with code. But Marlene says that she was on a budget; they opted for a more basic XML editor and actually write all their documentation in native XML. Rather than cumbersome, she says it’s quite easy and only takes about a week before the writers become accustomed to it. The XSLT transforms posed more difficulties, she says, but nothing insurmountable.

Topics in this Podcast

Topics in this podcast include the following:

  • DITA
  • XML and XML editors
  • DITA Open Source Toolkit
  • topic-based authoring
  • single sourcing
  • XSLT and transforms
  • Implementing DITA
  • adopting DITA

Helpful Resources

To contact Marlene Martineau, send an email to mmartineau@newdawntech.com. We love to hear feedback, so if you enjoyed the DITA podcast, let us know.

Madcap FlareAdobe Robohelp

By Tom Johnson

I'm a technical writer working for the 41st Parameter in San Jose, California. I'm interested in topics related to technical writing, such as visual communication, API documentation, information architecture, web publishing, JavaScript, front-end design, content strategy, Jekyll, and more. Feel free to contact me with any questions.

  • http://gui-yourself.blogspot.com avi

    Topic-based authoring and single-sourcing are technology independent. They could be implemented with RH, Word and probably other “legacy’ tools.
    My impression is that DITA is for the unlucky among us who are forced to use FrameMaker… :

    avis last blog post..Blog-like communication

  • Dan

    i can relate to this. we don’t have a large team too but we do get the job done. Flare helps quite a bit

  • Jess

    I think DITA is still too mysterious for wide-spread adoption. What are the formats to which writers publish? – print and online. If you have a tool that allows you to produce both print and online documentation from one source (single sourcing,) you’re in business. If you want a really complicated way to do this, choose DITA.

  • Dan

    Outlines sounds like the Table of COntents in Flare
    XSLT sounds like Targets in Flare

  • Shweta Shetye

    Hi Tom,

    This was the first Podcast I ever listened too, and I loved it. We in our organization use Epic Editor with a customized DTD and stylesheet for publishing the final outputs (PDF and CHM). I also use Framemaker (Unstructured) and agree with Marlene when she defines how limited the flexibility is with FM. Using Epic (I do not know if it qualifies as DITA) is much less cumbersome.

    I love working on it and recommend to others, if you have an open outlook to technology. Thanks for this amazing podcast:)


  • Pingback: » » DITA: From the Perspective of Someone Actually Using It Agile Cases()

  • http://www.janetswisher.com Janet Swisher

    I have a question for Marlene: You made a comment along the lines of “People think they need to have a content management system in order to use DITA”. Does that mean that you’re not using a CMS? In that case, how do you organize your source files?

  • Pingback: Game 28: #2 Seed I’d Rather Be Writing Versus #5 Seed Men With Pens | Writer's Resource Center()

  • Edward Dunlap

    Great interview, though I’m more inclined not to look at DITA now.

  • http://idratherbewriting.com Tom

    Edward, what changed your mind?

  • Pingback: Myths, Myths, Myths about Technical Writing | I'd Rather Be Writing - Tom Johnson()

  • Pingback: DITA: From the Perspective of Someone Actually Using It « Peter Bakker’s Sketches()

  • Julie

    Thank you for this most imformative podcast. I am embarking on a DITA implementation using Adobe’s Tech Comm Suite and DITA. The benefit of DITA is that it is designed to make the creation of software content consistent and reusable. DITA is not a tool. It is a schema, a methodology for writing. The benefit of structured FrameMaker and DITA is that FrameMaker enforces the DITA structure.