Template libraries
Templates are Confluence custom content stored under a per-space Capable Capable storage (capability markdown, feature 'templates') in either the current space or the global space, and can be created directly inside a catalogue folder. Only space and global templates can be targeted by a reference macro.
#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 |
Upload or paste an image into the document | Editor toolbar → + → Image 'From upload', paste from the clipboard, or drop the file on the editor |
Reuse one markdown document across many pages, kept in | Confluence editor → Markdown reference (Capable) / Markdown reference macro (Capable) |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Global settings → Permissions | - | Controls edit access to the GLOBAL asset store. Which is what governs who may create Global markdown templates. It is shared with diagrams, images, calendar and search because they all use one Confluence custom content t |
Global settings → Migration | - | Markdown is not on the tab's exclusion list, so the tab ships. |
#Worth knowing
A freshly inserted macro can poll for about two and a half minutes before giving up; a freshly created template can take several seconds to list.
#Limits that apply here
New-template catalogue polling
#Related
How it actually behaves.
