Change Details

As a product manager, I want to know whether a new feature that uses messages A, B, C... has been translated to languages X, Y, Z before deploying there. This could done with a new special page with two inputs: * List of languages * List of message keys For convenience, it would be helpful to be able to give prefix(es) of message keys. We have existing pattern processor, that would allow prefixes and more. It would be helpful if the results page could be easily be bookmarked and shared as a link. It would also be helpful to know whether all the translations have been exported and/or deployed, but this might require quite bit of more effort, so perhaps leave it out of scope for now and consider as follow-up. Operational considerations: * Since we only cache messages for message groups, not arbitrary list of messages, we should impose limits on the number of languages and message keys. See also {T59514} – difference is whether to use a list of message keys vs. a message group. # Design details We want to be consistent with similar stats pages such as [[ https://translatewiki.net/w/i.php?title=Special:LanguageStats&language=en-gb&group=citationhunt | Language stats ]] or [[ https://translatewiki.net/w/i.php?title=Special:MessageGroupStats&language=en-gb&group=citationhunt | Message Group stats ]]. Some specific considerations for the design of the new one: - Form for filtering. Which information/controls are provided for users to select a custom group of messages. - Entry points. How do users access this page, and how it is related to the similar Message Group stats one. - Information provided. Apart from the stats for the selected messages in each language, we may want to provide access to translate the missing messages (e.g., linking to the translation UI, or some intermediate page) - Performance limits. To prevent performance degradation we may want to provide some limits on the number of languages and messages that users can pick. We need to explore how to communicate those limits.

As a product manager, I want to know whether a new feature that uses messages A, B, C... has been translated to languages X, Y, Z before deploying there. This could done with a new special page with two inputs: * List of languages * List of message keys For convenience, it would be helpful to be able to give prefix(es) of message keys. We have existing pattern processor, that would allow prefixes and more. It would be helpful if the results page could be easily be bookmarked and shared as a link. It would also be helpful to know whether all the translations have been exported and/or deployed, but this might require quite bit of more effort, so perhaps leave it out of scope for now and consider as follow-up. Operational considerations: * Since we only cache messages for message groups, not arbitrary list of messages, we should impose limits on the number of languages and message keys. See also {T59514} – difference is whether to use a list of message keys vs. a message group. # Design details We want to be consistent with similar stats pages such as [[ https://translatewiki.net/w/i.php?title=Special:LanguageStats&language=en-gb&group=citationhunt | Language stats ]] or [[ https://translatewiki.net/w/i.php?title=Special:MessageGroupStats&language=en-gb&group=citationhunt | Message Group stats ]]. Some specific considerations for the design of the new one: - Form for filtering. Which information/controls are provided for users to select a custom group of messages. - Entry points. How do users access this page, and how it is related to the similar Message Group stats one. - Information provided. Apart from the stats for the selected messages in each language, we may want to provide access to translate the missing messages (e.g., linking to the translation UI, or some intermediate page) - Performance limits. To prevent performance degradation we may want to provide some limits on the number of languages and messages that users can pick. We need to explore how to communicate those limits. {F34429562, size=full} |{F34429564}|{F34429566}|{F34429568}|

As a product manager, I want to know whether a new feature that uses messages A, B, C... has been translated to languages X, Y, Z before deploying there. This could done with a new special page with two inputs: * List of languages * List of message keys For convenience, it would be helpful to be able to give prefix(es) of message keys. We have existing pattern processor, that would allow prefixes and more. It would be helpful if the results page could be easily be bookmarked and shared as a link. It would also be helpful to know whether all the translations have been exported and/or deployed, but this might require quite bit of more effort, so perhaps leave it out of scope for now and consider as follow-up. Operational considerations: * Since we only cache messages for message groups, not arbitrary list of messages, we should impose limits on the number of languages and message keys. See also {T59514} – difference is whether to use a list of message keys vs. a message group. # Design details We want to be consistent with similar stats pages such as [[ https://translatewiki.net/w/i.php?title=Special:LanguageStats&language=en-gb&group=citationhunt | Language stats ]] or [[ https://translatewiki.net/w/i.php?title=Special:MessageGroupStats&language=en-gb&group=citationhunt | Message Group stats ]]. Some specific considerations for the design of the new one: - Form for filtering. Which information/controls are provided for users to select a custom group of messages. - Entry points. How do users access this page, and how it is related to the similar Message Group stats one. - Information provided. Apart from the stats for the selected messages in each language, we may want to provide access to translate the missing messages (e.g., linking to the translation UI, or some intermediate page) - Performance limits. To prevent performance degradation we may want to provide some limits on the number of languages and messages that users can pick. We need to explore how to communicate those limits. {F34429562, size=full} |{F34429564}|{F34429566}|{F34429568}|