# Delivery

## Definition

Delivery is the final step of the process: the validated content reaches its audiences in the format and through the channel chosen at [project definition](https://docs.redaction-technique.org/en/tech-writing-process/project-definition/).

## Examples

The same source can surface as several different deliverables, for example:

- Animations published on streaming sites
- Brochures distributed at trade shows or provided to customers by sales engineers
- Newsletters sent to customers
- Updated website content
- Documents posted online as PDFs or distributed as printed guides, etc.

## Continuous publishing

In a [docs-as-code](https://docs.redaction-technique.org/en/docs-as-code/) workflow, delivery is automated: once a change is merged, a CI/CD pipeline rebuilds the deliverables and publishes them, so publication stops being a separate manual step (see the [CI/CD pipeline example](https://docs.redaction-technique.org/en/toolkit/example-cicd-pipeline/)). What still needs a deliberate decision is *when* documentation ships alongside a product release; the [release readiness checklist](https://docs.redaction-technique.org/en/toolkit/release-readiness-checklist/) covers that gate.

The same sources can also be delivered in machine-readable form, for scripts, search systems, or AI assistants rather than human readers. This manual does this itself: see [about this manual's API](https://docs.redaction-technique.org/en/about-the-api/).

## Related articles

- [Validation and quality control](https://docs.redaction-technique.org/en/tech-writing-process/validation-quality-control/)
- [Target format](https://docs.redaction-technique.org/en/tech-writing-process/target-format/)
- [Project definition](https://docs.redaction-technique.org/en/tech-writing-process/project-definition/)
- [Checklist: documentation release readiness](https://docs.redaction-technique.org/en/toolkit/release-readiness-checklist/)

---

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