# Three levels of technical documentation: wasteland, English garden, French garden

Why does technical documentation quality stall despite heavy investments in new authoring tools? Evaluating content maturity requires mapping documentation systems onto three gardening archetypes: the unmanaged wasteland, the cultivated English garden, and the strictly structured French garden.

Enters content maturity mapping. Document quality depends on three synchronized factors: process, team ownership, and semantic content format.

## Wasteland architecture

Unmanaged documentation lacks assigned ownership and standardized workflows. Authors produce disconnected files across arbitrary formats: a Word document in one folder, an unmaintained wiki page in another, and static PDFs exported years ago.

> **Wasteland ≠ bad writing:** A wasteland isn't defined by poor writing.

Accidental quality occurs when an engineer writes a clear guide during downtime. Without formal maintenance processes, single pages decay when products update.

## Topic-based English gardens

An English garden introduces dedicated ownership and consistent authoring workflows. Content team members maintain unstructured or lightweight topics using predictable tools.

Cultivating topic-based content provides reliable user documentation without XML schema complexity. Maintaining unstructured Markdown files in Git repositories delivers high accuracy without structured authoring overhead.

> **Often enough on its own:** For many teams, a well-maintained English garden is already far enough.

## Structured French gardens

A French garden introduces strict semantic constraints: content elements conform to rigid DITA or DocBook schemas rather than desktop publishing layouts.

<figure>
  ![Cartoon: Louis XIV in ornate fleur-de-lys robes wades knee-deep through a reedy marsh, asking a gardener ](https://redaction-technique.org/images/blog/three-levels-of-technical-documentation-louis.webp)
  <figcaption>The Sun King wants the French garden's deliberate order and would rather skip the informal English garden on the way: but the levels are climbed in turn, and for many teams the English garden is already far enough.</figcaption>
</figure>

Separating semantic payloads (warnings, prerequisites, steps) from presentation stylesheets allows automated single-source publishing across multiple languages and channels.

## Component interdependence

Adopting structured DITA schemas without establishing process discipline creates an expensive XML wasteland. Each maturity level requires alignment across all three pillars, as the matrix above shows:

<div class="not-prose my-5 flex flex-col gap-2">
  <div class="rounded-lg border border-amber-200 dark:border-amber-900/60 bg-amber-50/60 dark:bg-amber-950/20 text-amber-800 dark:text-amber-300 text-sm px-3.5 py-2.5 font-medium">DITA schema + weak process or ownership → an expensive XML wasteland.</div>
  <div class="rounded-lg border border-emerald-200 dark:border-emerald-900/60 bg-emerald-50/60 dark:bg-emerald-950/20 text-emerald-800 dark:text-emerald-300 text-sm px-3.5 py-2.5 font-medium">Process, ownership, and semantic structure rising together → structured publishing that works.</div>
</div>

## Maturity diagnostics

Diagnostic evaluation prevents premature migration to complex schemas:

1. **Establish process and ownership.** Teams in a wasteland must do this before changing markup formats.
2. **Run a content audit.** Measure current reuse requirements before committing to a DITA XML migration.

## Related reading

- [The three levels of technical documentation](https://docs.redaction-technique.org/en/costs/three-levels-of-documentation/): the maturity model in reference form.
- [Structured and unstructured formats](https://docs.redaction-technique.org/en/formats/structured-vs-unstructured-formats/): what makes a format semantic.
- [KISS Principle of Simplicity](https://docs.redaction-technique.org/en/costs/kiss-principle/): why restraint should govern each step up.

## External sources

- [Topic-based authoring](https://en.wikipedia.org/wiki/Topic-based_authoring)
- [Capability Maturity Model](https://en.wikipedia.org/wiki/Capability_Maturity_Model)

<small>*Hero image: ["The Ingenious Cottage Garden at Chatsworth, Derbyshire"](https://www.flickr.com/photos/22834654@N04/3491015252) by [UGArdener](https://www.flickr.com/photos/22834654@N04/), licensed under [CC BY-NC 2.0](https://creativecommons.org/licenses/by-nc/2.0/).*</small>

---

Source: https://redaction-technique.org/three-levels-of-technical-documentation