Content translation/Product Definition/Round Trip

CX's main use case is bootstrapping new article.

Consider the use case: As a Hindi Wikipedian, I want to translate an article about Hearbleed from English wikipedia to Hindi.

Scenario 1: User opens the English article, translates, publishes to target wiki. Usual wiki editing features are used for further edits. CX not used for later versions. Since CX created version 0, nothing to discuss about diffs.

Scenario 2: User opens the English article, translates, save as draft in Draft namespace(assume so). User come back to continue translation using Translation center. User must see all the previous translation without loosing any data. User publishes it like scenario 1 or repeats Scenario 2 any number of times. Diff between two versions in draft namespace should be clean. For example, if the user added a new paragraph, that alone should be the diff.

Scenario 3: User Published the article in main namespace and wanted to translate some more content from source language. We are yet to decide whether we allow editing a translation after publishing. If at all we are allowing it, it will be through the translation centre, available for the editor who bootstrapped it(first published). This is a complex use case since we lost the section alignment information. There could be n number of edits after publishing to main namespace too. Practically we need to assume that the source article and translated article are independent article. To be discussed.