What Capable Publishing is
Capable Publishing copies pages and folders from one Confluence space (the source) into another space (the target), and keeps a link between each original and its copy so you can refresh the copy later.
A space administrator turns it on for a space, picks the one target space, and chooses where copies land and whether the page tree is mirrored. From then on, content reaches the target space in exactly three ways:
Someone clicks Publish, Republish or Update in the page byline.
An approval on the page is approved and "Publish on approval" is switched on.
A space administrator runs a bulk job: Publish all pages, Publish approved pages, a selection from the Publishing space page lists, or an automatic structure rebuild after a settings change.
There is no scheduled or timed publishing.
Each publish copies the page with its attachments and labels, but not its page restrictions. Links to other pages in the same source space are rewritten to point at their published copies. Republishing updates the same target page as a new version, so you never end up with a second copy.
The byline shows the live state of every page: Published, Outdated, Out of sync, Moved, Failed, Missing target, Missing source, Unpublished or Unpublishable.
Publishing has no macros. You work with it through the page byline panel, a Publishing space page, a space settings tab and a Confluence admin settings tab.
#At a glance
Macros | None. This capability works through the page byline and its settings |
|---|---|
Sold as | A standalone app, and a capability inside the Capable Suite |
#A few things worth knowing
There is no scheduled or timed publishing. Nothing schedules a publish for a particular time.
The only non-manual source is Approval. Turning "Allow manual publishing" off therefore leaves approval-triggered publishing as the only route into the target space.
"Allow manual publishing" reads Off in the settings screen before your first save, but the value actually stored for an untouched space is manual plus automatic. Saving the form writes what the screen showed, which silently turns manual publishing off.
#Related
The short version.
