Translation
Documentation pages on Translation (8 pages).
This topic brings together 8 pages across the manual:
Learning path: 4. Choose an authoring modelDITA
Practical DITA XML solutions and tips developed through daily multilingual technical writing projects - structured authoring, topic reuse, conditional text, and publishing.
Case study: NuFirewall documentation
ReferenceLearning path: 4. Choose an authoring modelDITA
NuFirewall's documentation, praised by the press as a product strength, was built with DITA XML - a case study in structured authoring for software product documentation.
Learning path: 5. Build your toolkitChecklists
A gate checklist for whether documentation is ready to ship alongside a product release - coverage, accuracy, translation, and delivery.
Learning path: 6. Automation & legacy techniques
DITA XML structured authoring tutorials and XSL-FO stylesheet guides: create topic-based documentation and apply professional layouts for PDF and print output.
Learning path: 5. Build your toolkitWorked examples
A worked example of how to organize a docs-as-code repository - content by information type, locale-first for translated sites, and a clear separation from tooling.
Learning path: 4. Choose an authoring model
DITA XML structured authoring moves documentation from monolithic books to a modular content base, enabling topic reuse, efficient translation, and multichannel output.
Translation
ConceptLearning path: 2. Build a documentation process
Plan translation from the start of your documentation project: tackle it early to cut costs and delivery times, translate modular content in parallel with writing, and organize source repositories language-first.
Learning path: 3. Adopt docs-as-code
Use Git branches to manage parallel documentation projects, product variants, and translation workflows without conflicts - a practical guide for technical writers.