Change Details

We would like to streamline and scale the way we send newsletters to the various communities in the various languages that we work with. Currently, we find ourselves writing newsletters for English and then separate newsletters to be translated into other languages. The reason they are separate is because the English newsletters can be short and can link to our English project pages. But since the project pages aren't translated into other languages, the other newsletters need to contain information from the project pages. One idea to improve this is to translate portions of the project pages. Then we can link to project pages in our newsletters, and the single newsletter can be translated to all languages. The reason we don't want to translate entire project pages is because they get very long over time, and that may be too much to translate. Therefore the task here is to mark just the beginning portions of our project pages for translation, and then for those translations to be done before our next newsletter in March. @Trizek-WMF can decide how far down each of these pages to mark for translation, and if there are additional pages that should also be translated. [] https://www.mediawiki.org/wiki/Growth [] https://www.mediawiki.org/wiki/Growth/Understanding_first_day [] https://www.mediawiki.org/wiki/Growth/Personalized_first_day [] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Welcome_survey [] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Engagement_emails [X] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Newcomer_homepage [X] https://www.mediawiki.org/wiki/Growth/Focus_on_help_desk We would like the marked portions of these pages translated into Czech, Korean, and Vietnamese before we send our next team update, around March 15.

We would like to streamline and scale the way we send newsletters to the various communities in the various languages that we work with. Currently, we find ourselves writing newsletters for English and then separate newsletters to be translated into other languages. The reason they are separate is because the English newsletters can be short and can link to our English project pages. But since the project pages aren't translated into other languages, the other newsletters need to contain information from the project pages. One idea to improve this is to translate portions of the project pages. Then we can link to project pages in our newsletters, and the single newsletter can be translated to all languages. The reason we don't want to translate entire project pages is because they get very long over time, and that may be too much to translate. Therefore the task here is to mark just the beginning portions of our project pages for translation, and then for those translations to be done before our next newsletter in March. @Trizek-WMF can decide how far down each of these pages to mark for translation, and if there are additional pages that should also be translated. [] https://www.mediawiki.org/wiki/Growth [] https://www.mediawiki.org/wiki/Growth/Understanding_first_day [] https://www.mediawiki.org/wiki/Growth/Personalized_first_day [] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Welcome_survey [X] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Engagement_emails [X] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Newcomer_homepage [X] https://www.mediawiki.org/wiki/Growth/Focus_on_help_desk We would like the marked portions of these pages translated into Czech, Korean, and Vietnamese before we send our next team update, around March 15.

We would like to streamline and scale the way we send newsletters to the various communities in the various languages that we work with. Currently, we find ourselves writing newsletters for English and then separate newsletters to be translated into other languages. The reason they are separate is because the English newsletters can be short and can link to our English project pages. But since the project pages aren't translated into other languages, the other newsletters need to contain information from the project pages. One idea to improve this is to translate portions of the project pages. Then we can link to project pages in our newsletters, and the single newsletter can be translated to all languages. The reason we don't want to translate entire project pages is because they get very long over time, and that may be too much to translate. Therefore the task here is to mark just the beginning portions of our project pages for translation, and then for those translations to be done before our next newsletter in March. @Trizek-WMF can decide how far down each of these pages to mark for translation, and if there are additional pages that should also be translated. [] https://www.mediawiki.org/wiki/Growth [] https://www.mediawiki.org/wiki/Growth/Understanding_first_day [] https://www.mediawiki.org/wiki/Growth/Personalized_first_day [] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Welcome_survey [X] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Engagement_emails [X] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Newcomer_homepage [X] https://www.mediawiki.org/wiki/Growth/Focus_on_help_desk We would like the marked portions of these pages translated into Czech, Korean, and Vietnamese before we send our next team update, around March 15.