# Integrations

Diagrams are more useful when the rest of your documentation can see them: when search can find them, when Markdown can hold them, and when publishing a space publishes the diagrams properly rather than as flat pictures.

Nothing here is required. Capable Diagrams works on its own, and these are the joins that make it work better.

---

## What connects to what

| **Product**               | **What it adds**                               |
| ------------------------- | ---------------------------------------------- |
| Capable Search            | Find pages by the text inside their diagrams   |
| Capable Markdown          | Diagrams in fenced code blocks, as in a README |
| Capable Sites             | Published diagrams that keep their links       |
| Capable Diagrams for Jira | The same editors on Jira issues                |

---

## The pages

[Capable SearchFind pages by the diagrams on them with Capable Search, and pick up recent work from the diagrams tab.](https://help.gocapable.com/diagrams/capable-search.html)[Capable MarkdownEmbed a diagram in Capable Markdown with a fenced code block and edit it by changing the code.](https://help.gocapable.com/diagrams/capable-markdown.html)[Capable SitesHow Confluence diagrams are published by Capable Sites, and why a published diagram is a static image.](https://help.gocapable.com/diagrams/capable-sites.html)[Diagrams in JiraThe same six editors ship in Capable Diagrams for Jira. See what is shared and what differs from Confluence.](https://help.gocapable.com/diagrams/diagrams-in-jira.html)

---

## Related

[GuidesClickable diagrams, which is where publishing pays off.](https://help.gocapable.com/diagrams/guides.html)

[Security and privacyWhat anonymous site readers can see.](https://help.gocapable.com/diagrams/security-and-privacy.html)

[AdministrationEgress and rendering settings.](https://help.gocapable.com/diagrams/administration.html)

---

_Better with company._