[DOCU-518] Put all publishing docs in one place Created: 16/May/14  Updated: 07/May/15  Resolved: 07/May/15

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Ruth Stocks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PDF File Listener Based Synchronization.pdf    
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Documentation about publishing (activation) is badly scattered and difficult to find. Make Managing pages > Publishing a single, central place where a user can learn all essential things about publishing.

  • Terms. The term 'activation' is still around while the term 'publish' is taking its place in Magnolia 5. Explain to editors that for all practical purposes they are synonymous. You could say activation is the system process that copies content from an author to public instances whereas publishing also includes the user activity.
  • Scheduled publishing. Not covered at all for editors. Add a new section in Managing pages > Publishing. Explain what happens in the default 4-eye workflow when a workitem is scheduled. Include a screenshot of the Submit for publication dialog. The schedulePublication action is briefly mentioned in Enabling workflow in content apps as it should be but editors need to know this too. Explain in Publishing how to turn scheduled publishing on/off.
  • Publish-subscribe pattern. New users often wonder why two separate instances are needed. Magnolia's author/public instance model is very similar to the publish-subscribe pattern. The reasons and benefits are largely the same. Write a new paragraph in Instances, explaining the unfamiliar using the familiar. Link to it from the Publishing section or make a reusable chunk and include it in both.
  • Link to Disabling activation workflow
  • Link to Activation security


 Comments   
Comment by Antti Hietala [ 20/May/14 ]

Attached an excerpt from RĂ¼ping: Where Code and Content Meet that describes how the publish-subscribe software design pattern can be implemented in a CMS.

Comment by Ruth Stocks [ 27/May/14 ]

Updates at:

Generated at Mon Feb 12 01:09:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.