As part of MinT for Wikipedia Readers MVP (T359072), this ticket proposes to create the view for the machine translated version of an article. This view provides access to the automatically translated contents, and translation-related options. Access to options are provided through a floating element that acts as an always-visible indicator that contents are machine generated.
The user reaches this step from the Confirm step (T359512).
|Initial view|After scrolling|
|---|---|
|{F42543425, size=full}|{F42415217, size=full}|
# Design details
This step includes the following elements:
- **Header.** An "Automatic translation" label with a close action allows to inform the user they reached the translation and provide a way to leave (going back to the Home step, T359401). This step takes over the whole view for the user to focus on the activity (i.e., the general navigation and toolbars from the Wikimedia skin are not visible).
- **Machine translation indicator.** A compact one-line indicator. The indicator includes the `Robot` icon and labels for source and target languages separated by the `ArrowNext` icon to communicate the current set-up for the machine translaiton. The indicator is sticky, so that when the user scrolls and the indicator reaches close to the top of the viewport it becomes floating to remain always visible. Taping on the indicator provides access to the translation options. The menu and different options are covered in separate tickets.
- **Access to alternative workflows** After the translated title of the article, Options are provided in the contents to access original contents or contribute tot the translation which connect with two core wiki principles of verifiability and community contribution:
- Open in source language. A link with the label "Open in <source-language>" and an "external" indicator provides access to the article in the source language. The destination will open on a new tab/window.
- Review the automatic translation. A panel communicates both the contribution action, and a clarifying message to insist on the idea that machine translation is not always accurate. The "Review the automatic translation" action with the `Edit` icon directs users to the Content/Section translation workflow (with the article and languages pre-selected for the translation). The message "Automatic contents may be inaccurate" provides more context below.
- **Translated contents.** The machine translated version of the article is presented following the same style as the regular article contents.
- **Post-article notices.** After the article contents, in the usual footer style a couple of notices are included to provide more details on machine translation and, when available, human contents:
- The "Automatic contents may be inaccurate" label with a `Robot` icon and the message "This page is an automatic translation of content originally written in <source-language>." provides context about machine translation and a "Learn more" link to the [MinT project page](https://www.mediawiki.org/wiki/MinT) allows users to learn more about where translations came from.
- When the article already exists in the target wiki, another set of elements is shown. The "Human-created content is also available about this topic" label with a `UserGroup` icon and the message "Read the article from Korean Wikipedia editors to get more reliable information on the topic." provides context on human-created contents and contrasts with the above section. In addition, the local article is presented as a card (in the same way as in the "Confirm" step, T359512) allowing users to acces it on the target wiki (opening in a new window/tab).
## Loading translations
Wikipedia articles represent a potentially large amount of content to translate. We may want to consider some approaches that could provide a good user experience (getting the results as fast as possible) while minimizing wasted efforts (avoid requesting translation of contents that are not consumed by the users). We can consider:
- Non-blocking loading approach where content is shown as "loading" until it is available.
- Requesting translations as the user scrolls though the content.
- Pre-fetch some initial translations.
- Caching results to make it faster the next time.
From these techniques we can consider some that require low development effort for the MVP, and explore others in future iterations.
# Additional considerations
- Content in templates will be translated based on their rendered representation of the source template. For example, an article from English Wikipedia containing the "Infobox Album" is rendered as a table with multiple pieces of information. The contents of such table will be the ones translated to the target language. Not considering those as part of a template, and not trying to locate or adapt to the target language version of the template which may not even exists.
- Support for links is covered in {T359824}
- A proof-of-concept to explore how Wikipedia contents can be translated with MinT was created in T340956.
- [View in Figma](https://www.figma.com/file/RTBmXJ4ZGmhPoNP1nlnm5C/MinT-for-Readers-MVP?type=design&node-id=207%3A6889&mode=design&t=2vlNHNWKlZGeNk8u-1)
|{F42415210, size=full}|{F42415217, size=full}|