# Understand documentation

Start here if you're new to technical writing, or want a refresher on the principles behind everything else in this manual: why documentation is worth investing in, where documentation maturity comes from, how technical writing relates to technical communication, and how information types structure content.

  - [**Business case & strategy overview**](https://docs.redaction-technique.org/en/costs/): Maturity tiers, tooling costs, and documentation ROI — the argument for investing in a better process.
  - [**The three levels of technical documentation**](https://docs.redaction-technique.org/en/costs/three-levels-of-documentation/): Locate where your organization
  - [**From technical writing to technical communication**](https://docs.redaction-technique.org/en/costs/copywriting-to-technical-communication/): How the discipline differs from marketing and general copywriting, and why that distinction matters for process design.
  - [**Information types**](https://docs.redaction-technique.org/en/toolkit/information-types/): The architectural foundation: Concepts, Tasks, and References, their relationship to DITA, and how they shape our authoring templates.
  - [**The KISS principle**](https://docs.redaction-technique.org/en/costs/kiss-principle/): Why the simplest solution that solves the problem beats the cleverest one, and how that applies to documentation.

## How the rest of this manual builds on them

The sections that follow form a progression. Documentation is only as maintainable as its structure, so [structured information](https://docs.redaction-technique.org/en/tools-and-formats/) and [modular content](https://docs.redaction-technique.org/en/formats/modular-documentation/) come first. Modular text sources can be managed in [Git](https://docs.redaction-technique.org/en/docs-as-code/) like code, which makes automation and [CI/CD](https://docs.redaction-technique.org/en/toolkit/example-cicd-pipeline/) possible. Content that is structured and built automatically can then also be published in [machine-readable form](https://docs.redaction-technique.org/en/about-the-api/), for scripts, search systems, and AI assistants as well as human readers.

Once these foundations click, move on to [building a documentation process](https://docs.redaction-technique.org/en/process/) or jump straight to the [practical toolkit](https://docs.redaction-technique.org/en/toolkit/) for templates and checklists. For the foundational format choice, see [choosing an authoring model](https://docs.redaction-technique.org/en/tools-and-formats/). For unfamiliar terms, see the [glossary](https://docs.redaction-technique.org/en/reference/glossary/).

---

Source: https://docs.redaction-technique.org/en/learn/
