[DOCU-1489] Ways to synchronize content Created: 25/Apr/18  Updated: 29/Jun/18

Status: Open
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty

 Description   

Document the various ways you can synchronize content between Magnolia instances (author, public) and environments (dev, test/UAT, prod). What options do I have?

User stories:

As a developer, I need to synchronize content to a new public instance I created, so that the instance can deal with increased load.

As a developer, I need to synchronize content to a public instance that was down for maintenance, so that it has the same content as the other publics.

As a developer, I need to synchronize content between prod and UAT environments, so that my stakeholders can test a new template with fresh, realistic production content.

(ask Services for further use cases)

Several modules can solve the problem. Help the user choose the most appropriate one. Explain use cases and benefits for each.

Acceptance criteria:

  • I can find a summary or feature page about synchronization in documentation.
  • The page should be the first hit when searching "synchronization".
  • It's clear to me that I have several options.
  • The page helps me choose the appropriate mechanism.
  • The page guides me through use cases.
  • I can navigate from the page to more detailed info about each option.

Idea: Create a decision table (Choose the right app type) or decision tree (Multilanguage structure) to help the reader choose the most appropriate mechanism. ("If this...then that")


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