Change Details

From the suggestions section, pick an article for expanding. The article exist in target language. In the next screen observe that the 'New Translation' button is present. That should not be the case as the article already exist. When you resize the screen to mobile size, that button disappears. {F58430613}

From the suggestions section, pick an article for expanding. The article exist in target language. In the next screen observe that the 'New Translation' button is present. That option may be unexpected for a user that already selected a suggestion of an article to be expanded. In addition, when you resize the screen to mobile size, that button disappears. {F58430613} # Proposed approach The Confirmation step for an existing article can be reached from multiple places including (a) users searching for the article, and (b) users selecting it from the "Expand with new sections" part of the suggestions list. In each of them, users come with different expectations and the current set of actions proposed may not fit all of them. For case (a) the choice between starting a new translation or expanding the existing article makes sense. However, for case (b), the user already indicated the intention to expand the article and providing a "new translation" option can be confusing (i.e., could be interpreted as a new translation to expand it). As part of this ticket, we may want to explore the following ideas to improve the situation: - **Clarify confusion when coming from suggestions.** We need to consider ways to provide the functionality in ways that work for both (a and b) scenarios. Some options may include: (1) present the option to start a new translation in a way that works on both scenarios, or present the functionality in different ways on each scenario (either using different labels, or even hiding it in one of the cases). - **Button availability should be based on platform, not screen size.** That is, if we decide to provide an action to overwrite the article on desktop, the button should be visible on the desktop platform (regardless of the window size). - **Consider adjusting prominence.** When an article exists, we may want to encourage expanding it with new sections instead of rewriting it. Currently, the action to expand is emphasized with a primary button in comparison with the regular button used for "New translation". We may consider making the distinction.

From the suggestions section, pick an article for expanding. The article exist in target language. In the next screen observe that the 'New Translation' button is present. That should not be the case as theoption may be unexpected for a user that already selected a suggestion of an article already exist. Whento be expanded. In addition, when you resize the screen to mobile size, that button disappears. {F58430613} # Proposed approach The Confirmation step for an existing article can be reached from multiple places including (a) users searching for the article, and (b) users selecting it from the "Expand with new sections" part of the suggestions list. In each of them, users come with different expectations and the current set of actions proposed may not fit all of them. For case (a) the choice between starting a new translation or expanding the existing article makes sense. However, for case (b), the user already indicated the intention to expand the article and providing a "new translation" option can be confusing (i.e., could be interpreted as a new translation to expand it). As part of this ticket, we may want to explore the following ideas to improve the situation: - **Clarify confusion when coming from suggestions.** We need to consider ways to provide the functionality in ways that work for both (a and b) scenarios. Some options may include: (1) present the option to start a new translation in a way that works on both scenarios, or present the functionality in different ways on each scenario (either using different labels, or even hiding it in one of the cases). - **Button availability should be based on platform, not screen size.** That is, if we decide to provide an action to overwrite the article on desktop, the button should be visible on the desktop platform (regardless of the window size). - **Consider adjusting prominence.** When an article exists, we may want to encourage expanding it with new sections instead of rewriting it. Currently, the action to expand is emphasized with a primary button in comparison with the regular button used for "New translation". We may consider making the distinction.