# A single repository?

## Definition

Ideally, all content should be placed in a single repository, such as Git version control software. This maximizes reuse, consistency, and quality. If the content is in [DITA XML](https://docs.redaction-technique.org/en/formats/modular-documentation/) or DocBook format, for example, the *single-sourcing* capabilities of these formats can be fully exploited to publish the content in the appropriate form.

Content becomes a network of information modules, and the relationships within this network need to be managed, particularly during updates.

> **Diagram: Single repository feeding multiple deliverables**
>
> Diagram showing a single documentation repository feeding six deliverable formats: brochure, website, corporate magazine, white paper, user guide, and animation.

**Single Repository**

## Trade-offs

In practice, it appears that very few companies have taken this step. It is true that until structured formats are taught in secondary education, it seems unrealistic to expect all team members within a company to adopt them, especially if employee turnover is high. A [CMS](https://docs.redaction-technique.org/en/tech-writing-process/cms-workflow-and-reliability/) can help bridge the gap, but its reliability must be carefully evaluated.

**Additional resources**
- [Git: from file to content](https://docs.redaction-technique.org/en/tech-writing-process/git-from-file-to-content/)

## Related articles

- [Repository](https://docs.redaction-technique.org/en/tech-writing-process/repository/)
- [Version management systems - rustic but reliable](https://docs.redaction-technique.org/en/tech-writing-process/version-control-systems/)
- [Integrating documentation into development processes](https://docs.redaction-technique.org/en/tech-writing-process/integrating-documentation-into-development/)

---

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