Change Details

Users that start working on the first translation but leave the page may not be aware on how to get back to it. That could happen especially if users get into the translation editor from the beta campaign (T89701). Some possible solutions: - Send an #Echo notification when a user leaves the tool with the first translation incomplete. We can thank the user for starting a translation and let they know that they can continue it anytime from the Contributions page. We need to make sure that the notification is sent when there is a high confidence that the user left the draft editing and it is not conflicting with the notification of first-time publishing (e.g., the 1st publish notification replaces it if it was not read) - Capture the event of the user leaving the page. When the user tries to leave the editor, after having started the translation, and only the first time, we can interrupt the process to announce that the translation is saved and can be continued from the Contributions page. The above solution would be preferred since it is les annoying, but doing this once and only once can be acceptable.

Users that start working on the first translation but leave the page may not be aware on how to get back to it. That could happen especially if users get into the translation editor from the beta campaign (T89701) or they are not aware of the auto-save mechanism (assuming the work was lost). # Proposed solution Send an #Echo notification when a user leaves the tool with the first translation incomplete. The goal is to (a) make the user aware {F3515412} - Text copy: "Your translation for <page-name> was saved. You can continue this translation anytime, and publish it when it’s ready." - Main action: go to the translation dashboard with the in-progress view. We need to make sure that the notification is sent when there is a high confidence that the user left the draft editing and it is not conflicting with the notification of first-time publishing (e.g., the 1st publish notification replaces it if it was not read)

Users that start working on the first translation but leave the page may not be aware on how to get back to it. That could happen especially if users get into the translation editor from the beta campaign (T89701) or they are not aware of the auto-save mechanism (assuming the work was lost). Some possible# Proposed solutions: - Send an #Echo notification when a user leaves the tool with the first translation incomplete. We can thank the user for starting a translation and let they know that they can continue it anytime from the Contributions page. We need to make sure that the notification is sent when there is a high confidence that the user left the draft editing and it is not conflicting with the notification of first-time publishing (e.g., the 1st publish notification replaces it if it was not read)The goal is to (a) make the user aware {F3515412} - Capture the event of the user leaving the page- Text copy: "Your translation for <page-name> was saved. When the user tries to leave the editorYou can continue this translation anytime, after having started the translation, and only the first time, we can interrupt the process to announce that the translation is saved and can be continued from the Contributions page. The above solution would be preferred since it is les annoyingnd publish it when it’s ready." - Main action: go to the translation dashboard with the in-progress view. We need to make sure that the notification is sent when there is a high confidence that the user left the draft editing and it is not conflicting with the notification of first-time publishing (e.g., but doing this once and only once can be acceptable.the 1st publish notification replaces it if it was not read)