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):
- 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 supported in CX.
- When the user gets a notification of an article being translated (T88581), if the user receiving the notification does not have CX enabled, we can suggest to do so.
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:
- Article missing in a language. Instead of showing the red interlanguage link, we can show a notice to tell the user that the article can be translated to a language he knows with CX.
- Creating an article (T88600) supported as T89701: Ask users to try the ContentTranslation beta feature when creating an article.
- After article creation (T89697).
- When adding interlanguage links (T89700)