[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:
Several modules can solve the problem. Help the user choose the most appropriate one. Explain use cases and benefits for each.
Acceptance criteria:
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") |