Delivery
Delivery is the final step: validated content reaches its audiences through the format and channel chosen at project definition, from animations and brochures to newsletters, website updates, and printed or PDF guides.
Definition
Section titled “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.
Examples
Section titled “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
Section titled “Continuous publishing”In a docs-as-code workflow, delivery is automated: once a change is merged, a CI/CD (continuous integration and continuous delivery)Automation that checks every change as soon as it is submitted (continuous integration) and publishes the result once the checks pass (continuous delivery). In docs-as-code, a CI/CD pipeline builds the documentation, runs tests such as link and schema checks, and deploys the site.View in glossary → pipeline rebuilds the deliverables and publishes them, so publication stops being a separate manual step (see the CI/CD pipeline example). What still needs a deliberate decision is when documentation ships alongside a product release; the 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.