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.Capable MarkdownEmbed a diagram in Capable Markdown with a fenced code block and edit it by changing the code.Capable SitesHow Confluence diagrams are published by Capable Sites, and why a published diagram is a static image.Diagrams in JiraThe same six editors ship in Capable Diagrams for Jira. See what is shared and what differs from Confluence.
#Related
Better with company.
