# Target format

## Definition

The target format for technical writing is the medium through which the audience will access the content. This is distinct from the [source format](https://docs.redaction-technique.org/en/tech-writing-process/source-format/) in which the technical writer initially creates the content. The *single-sourcing* process allows multiple deliverables in various formats to be generated from a single source format.

## Examples

From validated source files, deliverables are generated using one of the following methods:

  
### <span role=

Fully Automatic</span>'>
    A white paper going from the DITA XML structured format to a PDF target format via the DITA-OT (DITA Open Toolkit).

  
### <span role=

Semi-Automatic</span>'>
    Content in DITA XML format exported to HTML, then pasted into a CMS.

  
### <span role=

Manual</span>'>
    A marketing brochure in word-processing format, or DITA XML laid out in InDesign, exported as PDF, then printed. Depending on how often the final document is published, XML import filters can also be set up to partially automate this step.

The more automated the process, the lower the risk of error, and the easier it is to publish and update. Automation also facilitates *single-sourcing*, enabling the generation of multiple deliverables in different target formats from the same source format. A project in DITA XML format can be delivered as a PDF file, Windows compiled help, JavaHelp, an HTML site, and more — the [formats and tools](https://docs.redaction-technique.org/en/costs/formats-and-tools/) article explains how the choice of format shapes these possibilities. In this regard, XML offers nearly unlimited possibilities.

Lightweight formats follow the same principle. In a docs-as-code workflow, Markdown sources are typically built by a static site generator into an HTML site, and publishing is a pipeline step rather than a manual one (see [delivery](https://docs.redaction-technique.org/en/tech-writing-process/delivery/)). Target formats are no longer only for human readers: this manual is generated from Markdown into HTML pages, and also into per-page Markdown files and JSON indexes for scripts and AI assistants (see [about this manual's API](https://docs.redaction-technique.org/en/about-the-api/)).

## Related articles

- [From document to modular document base](https://docs.redaction-technique.org/en/formats/modular-documentation/)
- [Structured and unstructured formats](https://docs.redaction-technique.org/en/formats/structured-vs-unstructured-formats/)
- [The Raspberry Pi 3 as a documentation platform](https://docs.redaction-technique.org/en/tutorials/raspberry-pi-documentation-platform/)

---

Source: https://docs.redaction-technique.org/en/tech-writing-process/target-format/