Maintaining a healthy DITA project
There are lots of aspects necessary to have a happy and healthy DITA project. Project structure, version control, work-flow, custom validation rules, an internal style guide, tools to perform batch modifications, automation of the publishing processes, automation of the project-wide validation checks, ways to quickly ask and receive feedback from engineers, ways to requests and receive feedback from end users. When implemented, all these aspects lead to more consistent outputs, reduce the technical writers’ stress and lets them focus on the task at hand. We will go through each of these aspects, I will show you examples of how we collaborate on our DITA based user’s manual and maybe together we’ll find some best practices leading to a successful DITA proje
What can the audience expect to learn?
You will learn various ways in which you can automate publishing and validation tasks, you will see examples of custom structure consistency checks and maybe enrich and enlarge your own internal style guide rules. We’ll discuss various work-flows and ways of obtaining feedback from engineers or from end users. And we’ll discuss how we can increase the technical writer’s voice and importance in the company.
Meet the presenter
Radu Coravu started working more than 10 years ago as a software developer for Syncro Soft Ltd., the manufacturer of the popular Oxygen XML Editor. During the last years, his main focus has been in the development of the visual XML Author editing environment and the specific-DITA support provided by Oxygen. He provides support for complex integrations and helps steer the product in the right direction, all this with some development on the side.