# Too complex a document architecture?

## Definition

DITA XML enables significant productivity gains by reducing the volume of content that the technical writer creates, translates, and maintains. However, this productivity gain involves increased complexity, as explored in [structured and unstructured formats](https://docs.redaction-technique.org/en/formats/structured-vs-unstructured-formats/).

## Trade-offs

While DITA XML projects are more *complex*, they are still less *complicated* than projects based on more traditional formats like FrameMaker. This is because DITA XML follows a logical architecture. As a result, the technical writer can rely on the predictable behavior of the tools used, avoiding the *tricks and hacks* needed to work around bugs or the erratic behavior of more cumbersome tools.

> **Diagram: DITA XML is complex but predictable, traditional formats are complicated and erratic**
>
> Cynefin framework diagram placing DITA XML in the complex domain, since its behavior is rational and predictable despite its complexity, and traditional formats like FrameMaker in the complicated domain, due to their erratic behavior requiring workarounds and hacks.

**DITA XML is complex but predictable; traditional formats are complicated and erratic.**

## Examples

The following overview presents the different levels of complexity introduced by DITA XML and the solutions that help the technical writer manage them more effectively:

  
### <span role=

DITA XML syntax</span>'>
    **Solution:** IDE (Integrated Development Environment) such as XMetaL or nXML

  
### <span role=

Relationship management between atomic information building blocks</span>'>
    **Solution:** A dedicated CMS (Content Management System) such as Componize or DocZone

  
### <span role=

XSLT stylesheet syntax</span>'>
    **Solution:** Graphical stylesheet creation software

For a small technical writing team, the primary challenge will be applying the company's visual identity to the output. Other aspects can be managed without specialized tools, through effective communication and a series of best practices — one of the most important being the [KISS principle of simplicity](https://docs.redaction-technique.org/en/costs/kiss-principle/).

## Related articles

- [From document to modular document base](https://docs.redaction-technique.org/en/formats/modular-documentation/)
- [Case study: NuFirewall documentation](https://docs.redaction-technique.org/en/formats/nufirewall-case-study/)
- [Formats and tools](https://docs.redaction-technique.org/en/costs/formats-and-tools/)

---

Source: https://docs.redaction-technique.org/en/formats/document-architecture-complexity/
