# GitHub-Flavored Markdown rendering Remark-gfm 4 (tables, task lists, strikethrough, autolinks, footnotes), GitHub blockquote alerts, heading slugs with autolinks, and Prism syntax highlighting. Capable adds rehype-sanitize and skipHtml on top. --- ## Where you do it | **Task** | **Where** | | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | | Add a markdown document to a page | Confluence editor → /Markdown (Capable) \[Suite\] or /Markdown macro (Capable) \[standalone\], or the Markdown byline entry on a published page | | Show a border and a title on the macro | Configure Markdown → 'Show border' checkbox and the 'Markdown title' field | | Point a macro at a README on GitHub, GitLab or Bitbuck | Configure Markdown → Markdown from URL | --- ## Settings that affect this | **Setting** | **Where** | **What it does** | | ---------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Global settings → Capabilities → Markdow | \- | Hiding Markdown removes it from the Capable nav bar and the content byline menu across the site (app property capable-global-hidden-capabilities). It does NOT stop existing macros from rendering. | | Space settings → Space Capability Settin | \- | Auto shows the byline entry only when the page already carries markdown; Always pins it in every page's byline in that space; Never hides it there. Stored on the space property \_capable under capabilities.alway | | Global settings → Features → AI integrat | \- | 'Allow AI-powered features across Capable. Turn off to disable AI for all users.' Turning it off removes the Studio (Generate markdown with AI) section from the markdown catalogue. Studio additionally requires the app's | --- ## Worth knowing * The document macro's 'Markdown description' field is captured but never saved, while the unsaved-changes guard still counts editing it as a change. * The self-hosted diagram renderer is currently inert for markdown fences. * 'Copy as macro' is unavailable for the bundled Examples and for URL- or attachment-sourced markdown. * Hiding Markdown globally removes only the nav and byline entries; existing macros keep rendering. * Markdown assets never get a thumbnail or preview anywhere. By design. * On a published Capable Site markdown is re-rendered by a different engine, so the static page can differ visibly from the Confluence page, and diagram fences become code blocks. --- ## Related [Diagrams from fenced code blocksAnother part of how this works.](https://help.gocapable.com/markdown/diagrams-from-fenced-code-blocks.html) [Markdown library pageAnother part of how this works.](https://help.gocapable.com/markdown/markdown-library-page.html) [How it worksThe rest.](https://help.gocapable.com/markdown/how-it-works.html) --- _How it actually behaves._