Integration of Content Translation (CX) and Visual Editor (VE) is supposed, at first, to change the contenteditable editing component to VE and preserve the current CX functionality—and nothing else. It is important to ensure that features already available in ContentTranslation are retained and these would specifically be:
**Immediate priority:** (total time estimate: 9 person-days)
# [ ] [ST w/ help from DC, ES] Being able to publish pages to the target wiki (there is no publish button in the interface at present) [1d] T162768
## [ ] Translation should be saved as translator edits (autosave) [0.5d]
## [ ] Restoring a saved translation against the version of the source article on which it was initiated. The translated text must be loaded with the same content as it had when it was auto-saved. (presently it does not save or load(!!!)) [0.5d]
# [ ] [ST] In case that machine translation is not available, null MT so that, if the user selected “source text”, the target text must be pre-filled with the (adapted) source text [0.5d, or may be working already]
# [x] [ES] Presently you can add a link to the source text, which is not correct (the source text should not be writable at all!) [0.5d]
# [ ] [NL&ST] template adaptation for a few important templates [5d] T162114
# [ ] [RK] Feed existing (server-side) adapted categories into VE [1d]
# [ ] [Adaptation] Preserve the template editor functionality: the ability to adapt each parameter in the UI. [some weeks]
# [ ] [Initial load] The “+ Add translation” placeholder must be shown in the first section on load
# [ ] [Prefilling translations] If the user selected “//no automatic translation//”, it must remain empty.
# [ ] [MT/Adaptation] UI for the user to select between different MT engines / null MT
# [ ] (Better alternative to 3) Restoring a saved translation against a changed source article. [2+ days? hard cut-off=??]
# [ ] [MT/Adaptation] When the user switches between different MT [Apertium/Yandex etc] options, those will preserve any changes the user made to their content. An additional option to reset to the initial content will be available when the content has been modified.
# [ ] [MT/Adaptation] A warning card is shown when the user has added automatic content without editing above a defined threshold.
# [ ] [MT/Adaptation] If text is selected in the target column that can be linked to an existing article in the target wiki, the link tool must be shown that allows to link to it.
# [ ] Clicking a link in the source column must show a link card with the source article (with title and image if available). If a directly corresponding target article exists, it must be shown, too. The link card must allow adding the link to the translation.
# [ ] Clicking a reference [in the source column?] must show a reference card in the sidebar. The card must have a button that adds the reference to the translation.
# [ ] References and Math must be auto-added to the automatic translation. [Is this also adaptation? Or is it different?]
# [ ] Integration with abuse filter and checking that it works
# [ ] [UI] Link tool to be as close to the CX1 one as feasible in terms of UX (in the third column, rather than as an inspector)]
# [ ] [UI] Rest of the system to be as close to CX1 as feasible in terms of UX
# [x] [Adaptation] image adaptation [done; is the bug with block images breaking segmentation fixed already? Yes it is fixed Sweet! AFAIK]
# [x] [Adaptation] reference adaptation [done, but since most refs contain templates it doesn't work in most practical cases yet, it will "magically" work when template adaptation is done]
# [x] he source column must show a loading indicator.
# [x] The translation column must have no content.
# [x] The “+ Add translation” placeholder must be shown in other sections on hover.
# [x] Source and target paragraphs remain always vertically aligned. If the user extends a paragraph in the translation by adding more content, the paragraphs below will be automatically pushed down to keep the visual alignment.
# [x] Hovering over a source or target paragraph highlights in yellow the corresponding one.
# [x] Link adaptation must work automatically when using automatic translation (see above).
# [x] It must be possible to add a link to a non-existing (“red”) target article.
# [x] //Not required for the MVP, but we can consider support for adding new templates using VE's buttons and forms to the translation if it does not require extra work.//
# [x] //Not required for the MVP, but we can consider support for editing or adding new elements using VE's buttons and forms if this doesn't require extra work.//