17 bundled starter templates

Read-only examples in three folders. General purpose (Checklist, Blog post, FAQ, Tutorial), Technical documentation and Project Planning (Process flow, Product requirements, Project proposal, User journey, Release notes, Meeting notes). Their storage type is BUILT_IN: they cannot be edited, deleted or referenced. Using one copies its body into a new document.

#Where you do it

The Capable Markdown catalogue with Examples expanded in the left nav into General purpose templates, Technical documentation and Project Planning. The Technical documentation folder lists API Documen — Technical documentation is one of the three folders holding the read-only examples that ship with the app.

Task	Where
Turn a library template into a macro by pasting a link	Capable Markdown catalogue → a template's share menu → Copy as macro, then paste into the editor
Save a document to the shared library	Capable Markdown page → Templates → Space templates or Global templates → Create
Turn markdown that lives on a page into a reusable tem	Capable Markdown page → open the page-owned document → 'Save as template', or drag it from 'Markdown on pages' onto a Templates section or folder

#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.

Version history

Another part of how this works.

Remix and Save as template

Another part of how this works.

How it works

The rest.

How it actually behaves.