How to approach technical writing as an engineering discipline — from project definition to version control, automated testing, quality validation, and delivery.
- [**Project definition**](https://docs.redaction-technique.org/en/tech-writing-process/project-definition/): Define audience, scope, and deliverables before writing - five project parameters every technical writing engagement needs. - [**Integrating documentation into development**](https://docs.redaction-technique.org/en/tech-writing-process/integrating-documentation-into-development/): Treat docs like code: same release cadence, same version control, same review process. - [**Git: from file to content**](https://docs.redaction-technique.org/en/tech-writing-process/git-from-file-to-content/): Git stores content blobs, not filenames - understanding that model makes branching and diffing documentation much simpler. ## Structured DITA XML formatHow structured and unstructured documentation differ — topic-based authoring, single-sourcing, and modular document architecture without vendor lock-in.
- [**Case study: NuFirewall documentation**](https://docs.redaction-technique.org/en/formats/nufirewall-case-study/): Press reviewers cited the documentation as a product strength, not a supplement. A detailed look at the DITA XML techniques that made it possible. - [**Structured and unstructured formats**](https://docs.redaction-technique.org/en/formats/structured-vs-unstructured-formats/): DITA - [**From document to modular document base**](https://docs.redaction-technique.org/en/formats/modular-documentation/): Replace monolithic manuals with reusable topic modules: lower translation costs, parallel reviews, multiple output formats from one source pool. ## The business case for structured documentationWhy documentation architecture matters to an organization — maturity models, long-term maintenance costs, and technical communication economics.
- [**From technical writing to technical communication**](https://docs.redaction-technique.org/en/costs/copywriting-to-technical-communication/): Technical communication starts before the sale - why the role spans marketing, journalism, and product documentation. - [**The three levels of technical documentation**](https://docs.redaction-technique.org/en/costs/three-levels-of-documentation/): A three-tier maturity model - wasteland, topic-based, structured DITA - to locate where your organization sits and what the next level costs. - [**Formats and tools**](https://docs.redaction-technique.org/en/costs/formats-and-tools/): Choose your source format before your tool - the format determines vendor lock-in, automation options, and long-term costs.View all 5 strategy & economics articles
## TutorialsPractical implementation guides and tooling — step-by-step instructions for DITA-OT, XSL-FO, Sphinx, Python regular expressions, and automation scripts.
- [**DITA XML and XSL-FO tutorials**](https://docs.redaction-technique.org/en/tutorials/dita-xml-xsl-fo-tutorials/): Set up the DITA XML to PDF publishing chain with XSL-FO - step-by-step from source authoring to styled output. - [**Conditional text with Sphinx**](https://docs.redaction-technique.org/en/tutorials/conditional-text-sphinx-rest/): Generate document variants from the same ReST sources with Sphinx conditional text. - [**Regular expressions in Python**](https://docs.redaction-technique.org/en/tutorials/python-regular-expressions/): Python --- Source: https://docs.redaction-technique.org/en/