Capable Sites export
When a page is published to a Capable Site, the PDF is copied into the published site at build time and rendered there. Zoom, Slider page navigation and Download carry over.
#Where you do it
Task | Where |
|---|---|
Install it | Atlassian Marketplace, or get it as part of the Capable Suite |
Insert the macro on a page | Confluence editor: type / and search "PDF embed (Capable)", or use the Capable macro browser under Media |
Embed a PDF from a public web address | Macro config > Types of file = Public URL > PDF URL |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Get started page | Shown after install | - |
Approved external domains (Capable Suite | Capable Suite admin > Capable settings > Egress | - |
Edition | Capable Suite capability list | - |
#Worth knowing
PDFs loaded from a web address pass through Capable's hosted proxy, so the file bytes transit Capable infrastructure. Attachments do not.
Exporting a Confluence page to PDF or Word does not render the embedded PDF.
If nothing can be resolved at site build time the published page shows a plain note that the PDF could not be exported.
In the Capable Suite, an admin cannot hide or disable PDF Embed from the Capabilities list, because it is a macro-only capability.
#Related
How it actually behaves.
