Working with other capabilities

Most of what makes Markdown worth having in the suite comes from what sits next to it. This page is the summary; each connection has its own page with the detail.

Where a connection doesn't exist, it's listed as such rather than left out, so you can stop looking.


#Every connection

Connects to

What you get

Capable Sites (published static sites)

Both macros publish as properly formatted content. Images from other websites are copied onto the site. The document macro's Title and the reference macro's template title both become a heading.

Kroki diagram gateway

Diagrams written in markdown are drawn by a Capable service and shown as images, not drawn in your browser. This needs a Capable client token. The option to use a renderer you run yourself is currently switched off, so every markdown diagram goes through the Capable service.

Capable URL proxy and egress

Markdown from a URL is fetched through the Capable proxy. If the website is on your site's approved list, your browser fetches it directly instead. The app itself can only contact Capable's own services.

Confluence custom content types

Markdown documents are stored as two kinds of Confluence content, and their names differ by product. The standalone app uses 'Capable Custom Content (Markdown)' and 'Capable Shared Storage (Markdown)'. In the Suite, both have '(Suite)' on the end. Neither allows duplicate titles, both are searchable, and both are open to unlicensed and anonymous readers.

Content indexing and CQL aliases

Markdown indexing records which templates a page uses, so you can find those pages with a Confluence search (CQL). Pages are re-indexed automatically whenever markdown is created or updated.

Rovo agent

The standalone app has its own Rovo agent, 'Capable Markdown', with four conversation starters. It can write markdown documents onto pages from Rovo chat. In the Suite, a single combined agent does the same job.

MCP surface

Markdown is available to the Capable agent, but it isn't offered to third-party agents in either product. Markdown documents never get a thumbnail.

Navigation entry points

Standalone: a 'Capable Markdown' space page, global page and global settings page, all open to unlicensed and anonymous visitors. Suite: one shared 'Capable' space page, global page and settings page, plus a second byline entry titled just 'Capable' (keyboard shortcut ',').

Macro migrators

Run these from the Migration settings tab.


#The pages


#A few things worth knowing

  • A connection needs both halves installed. In a standalone app, most of these don't exist.

  • Anything that depends on search only reflects pages that have been indexed.

  • Published sites render Capable macros properly, which is where several of these pay off.



Better with company.