# Technical documentation

📝

Technical teams use Capable Diagrams to explain how systems, services, data flows and infrastructure fit together. 

These diagrams make technical context easier to understand for engineers, architects, product managers, support teams and stakeholders.

## [#](#typical-scenarios)**Typical scenarios**

### [#](#system-context-diagrams)System context diagrams

Show users, products, services and external systems.

![Context Diagram](https://help.gocapable.com/images/att1248723042.svg)

### [#](#architecture-diagrams)Architecture diagrams

Applications, platforms, integrations, cloud infrastructure or data pipelines.

![Architecture Diagram](https://help.gocapable.com/images/att1248788564.svg)

![Component Diagram](https://help.gocapable.com/images/att1249542220.svg)

### [#](#sequence-diagrams)Sequence diagrams

Explain how systems interact during key transactions or incidents.

![Sequence Diagram](https://help.gocapable.com/images/att1248690255.svg)

![Sequence Diagram](https://help.gocapable.com/images/att1248297072.svg)

### [#](#network-and-deployment-diagrams)Network and deployment diagrams

Document environments, regions, dependencies and ownership.

![Deployment Diagram](https://help.gocapable.com/images/att1249607775.svg)

![Network Diagram](https://help.gocapable.com/images/att1248854154.svg)

### [#](#other-diagrams)Other diagrams

Runbooks, design decisions, implementation plans and support documentation.

![Capable Apps](https://help.gocapable.com/images/att1248886870.png)

## [#](#how-teams-use-it)**How teams use it**

* Architects sketch high-level system context before moving into detailed service or deployment views
* Engineers use diagrams in design pages to explain proposed changes before implementation
* Support and operations teams use architecture diagrams to understand dependencies during incidents

ℹ️

**Best practice:** Keep different levels of detail separate. Use one diagram for the system context, another for component detail, and another for deployment or runtime behaviour.

## [#](#why-capable-diagrams-helps-here)**Why Capable Diagrams helps here**

* Gives technical pages a visual entry point before readers go into detailed design notes
* Helps teams review architecture decisions and spot missing dependencies
* Supports common technical formats such as Mermaid, PlantUML, C4-style modelling and visual sketching
* Makes diagrams part of Confluence documentation instead of separate files that go stale

## [#](#useful-follow-up-pages)**Useful follow-up pages**

* [Simulate BPMN Diagrams in Confluence](https://loom.com/share/81084bde0666425a82f3086de0c2b23e)
* [Interactive diagrams](https://innovator.atlassian.net/servicedesk/customer/portal/3/article/661192771)
* [Using the Capable editor](https://innovator.atlassian.net/servicedesk/customer/portal/3/article/884932617)
* [Capable Diagrams: Visualizing Workflows with Ease](https://innovator.atlassian.net/wiki/spaces/CAP/pages/445022274)