Pay no GREAT attention to that man behind the curtain
Every department has its resident tech wizard: the maintainer of the templates, the DITA Open Toolkit, the wiki, and so on. What happens when that wizard flies off to a new kingdom?
Every department has its resident tech wizard: the maintainer of the templates, the DITA Open Toolkit, the wiki, and so on. What happens when that wizard flies off to a new kingdom?
In this webcast recording, Simon Bate discusses the pros and cons of using the DITA Open Toolkit. Topics include localization, automation, open standards, and plugin architecture on the pro side; plugin architecture, PDF configuration, open standards, and documentation on the con side.
Reuse and automated formatting are the most common justifications for XML, but recently, we have heard a new reason from several customers: rebranding.
In the world of superheroes, technical writers could just slide down a pole or do a clandestine spin to transform themselves into DITA technologists. Of course, nothing is that easy, so what does the transformation from tech writer to DITA superhero really require?
Deciding on a content model is a critical step in many of our projects. Should it be DITA or something else? The answer, it seems, often has more to do with our client’s corporate culture than with actual technical requirements.