[LIVECOPY-381] DOC: Secondary LC improvements post-migration Created: 12/Jan/23  Updated: 09/Feb/23  Resolved: 09/Feb/23

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Alex Mansell Assignee: Alex Mansell
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
relation
is related to LIVECOPY-384 DOC: Live copy feedback Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
LIVECOPY-326 DOC: Improve Live Copy documentation ... Sub-task Closed Adrian Brooks  
LIVECOPY-374 DOC: Explain how the translation work... Sub-task Closed Adrian Brooks  
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: LC enablement
Sprint: AuthX 27, AuthX 28
Story Points: 5
T-Shirt Size: Medium
Team: AuthorX
Work Started:

 Description   

This secondary story is to follow the LIVECOPY-376 revamp migration and should address the following:

  • Introduction (use cases) Take from Feature Brief
  • Decision Tree (take from slide)
  • Translation flow (translation goes to master/managed in master) the translation happens at master level. And then each live copy would get its own language. You'll need access to master.
    • Translation flow with incubator module (see feature brief)

Tasks

Remove:

  • Your goal is to limit content duplication, hence reducing the manual localized effort to maintain your multi-installation websites.
  • REPLACE WITH minimizing effort instead of limiting duplication
  • Centralized tabs (remove both) just call them use cases for Live Copy.

Add:

  • How it works page (under introduction) middle box/column of Miro board

 

Resources

 

Translation notes:

From Tobias:

your are right the main flow is configuring/adding them in the master and push them to the live copy pages.
I think a few bullet points could be:

The translation can be made faster by using the translation support modules

If a local editor wants to change a text provided by the master its no problem but he has to protect the value by protecting either the field,  the component or the page

Doing the whole translation in the live copy child page would create a big mess so should be a red flag


Generated at Mon Feb 12 02:28:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.