Suite or standalone
Publishing is sold on its own and as part of the Capable Suite. The features are the same in both; several behaviours around them are not.
#What differs
Topic | What differs |
|---|---|
Which apps include Publishing | Three apps include the whole Publishing capability, not two: Publishing for Confluence (standalone), Capable for Confluence (the Suite), and Approval for Confluence. Customers of the Approval app get the full Publishing feature set even though the app is not named after it. Everything on this page therefore comes in three variants. |
Where the byline appears | In the standalone Publishing app and the Approval app, the "Capable Publishing" byline appears on every page the user can view (subject to the site-wide Hidden setting and the space's Never setting). In the Suite it also needs the space to have Publishing set to "Always", or the page to already carry a publish record. |
What the app is called | Standalone Publishing app: the space page, global page, space settings tab and global settings tab are all titled "Capable Publishing". Suite: they are all titled "Capable", with Publishing as a section named "Publishing" inside the Capable space settings tab. Approval app: they are titled "Capable Approval", again with a "Publishing" section. |
Publishing when a page is approved | Works in the Suite and in the Approval app. The standalone Publishing app does not include Approval, so pages can never be published on approval there, and the "Publish approved pages" button is not shown. |
Deleted pages | The Suite responds when a page or blog post is deleted. The standalone Publishing app and the Approval app do not. |
Search and saved searches | Each app names its publish record, and all 13 of its search fields, with its own prefix. "Publish status" in the Publishing app, the Approval app and the Suite are three different fields. A saved search or CQL query written for one app will not match another, and moving between apps loses all existing publish search data. |
Content types | Supporting content types appear as "Capable Custom Content (Publish)" and "Capable Shared Storage (Publish)" in the standalone app, and with "(Suite)" in the Suite. These show up in Confluence content type lists and search. |
Anonymous and unlicensed viewers | The Publishing byline needs the viewer to be logged in, so anonymous readers never see it in any app. In the standalone Publishing app, the space page and global page do allow unlicensed and anonymous viewers, but they only see a fixed "Powered by Capable" notice rather than any publishing data. |
Edition and help | Publishing is a standard-edition capability and is available on both Suite editions. Help lives at https://help.gocapable.com/confluence-publishing/. |
#A few things worth knowing
Macro names usually differ: the standalone app tends to add the word macro.
Content is not shared between the standalone app and the suite, so moving across is a migration.
Anything described as working with another Capable feature needs that feature installed too.
#Related
Same features. Different neighbours.
