Change Details

Inform users that have not tried Content Translation yet, that they can enable the beta feature. There are several kinds of events that the information can be attached to in order to make it relevant: **Beta feature related events** - History view. Show a tooltip the first time a user checks the history of an article crated with Content Translation. Th tooltip will point to the CX tag, and allow users to enable the feature to try it by themselves. - After new languages (relevant to the user are added to CX. **Contribution entry points** Some of the proposed entry points for translation can be extended to those users with the feature disabled to encourage them to enable it: - Creating an article (T88600). - After article creation (T89697)

Inform users that have not tried Content Translation yet, that they can enable the beta feature. There are several kinds of events that the information can be attached to in order to make it relevant (we should make sure that we don't inform about the existence of the feature more than once for each user, even if several mechanisms are supported): **Beta feature related events** - History view. Show a notice the first time a user checks the history of an article crated with Content Translation. The notice will point to the CX tag, and allow users to enable the feature to try it by themselves. - Add to watchlist. After a user adds a page to the watchlist we can announce that the page was created a s a translation and ask the user to activate the feature to keep translating. - Thank the author. After thanking the author we can inform that the page was a translation and encourage the user to try the feature. - After new languages (relevant to the user are added to CX. **Contribution entry points** Some of the proposed entry points for translation can be extended to those users with the feature disabled to encourage them to enable it: - Creating an article (T88600). - After article creation (T89697)

Inform users that have not tried Content Translation yet, that they can enable the beta feature. There are several kinds of events that the information can be attached to in order to make it relevant (we should make sure that we don't inform about the existence of the feature more than once for each user, even if several mechanisms are supported): **Beta feature related events** - History view. Show a tooltipnotice the first time a user checks the history of an article crated with Content Translation. The notice will point to the CX tag, and allow users to enable the feature to try it by themselves. - Add to watchlist. Th tooltip will point to the CX tag,After a user adds a page to the watchlist we can announce that the page was created a s a translation and ask the user to activate the feature to keep translating. - Thank the author. and allow users to enable the feature to try it bAfter thanking the author we can inform that the page was a translation and encourage the user to try themselves feature. - After new languages (relevant to the user are added to CX. **Contribution entry points** Some of the proposed entry points for translation can be extended to those users with the feature disabled to encourage them to enable it: - Creating an article (T88600). - After article creation (T89697)