As part of the work on Custom translation suggestions (T113257), support was provided to define collections of topics to translate to make them visible in Content Translation on mobile (T378958). Currently, only one collection is available for users, which is a hardcoded collection based on vital articles (T374597). With only one collection users may not understand the potential of collections, the option for "all collections" becomes redundant, and a "special" collection does not serve as an example for communities to discover how collections are created.
{F57725403 size=full}
This ticket proposes to add more collections by using the `<page-collection/>` tag on existing pages that list relevant articles. As part of this process, we'll check with communities whether there is any objection for their list of articles to be visible in Content Translation. These are the proposed pages to mark as collections:
- [List of articles every Wikipedia should have](https://meta.wikimedia.org/wiki/List_of_articles_every_Wikipedia_should_have). Similar to the current vital articles but defined on Meta (not English Wikipedia), will reflect community updates and has a more manageable size (limited to 1000 items, compared to the 50000 vital articles).
- [Wikiproject Women's Health Vital articles](https://meta.wikimedia.org/wiki/Wikiproject_Women%27s_Health/Vital_articles). Aligned with [Wikimedia Foundation annual plan Key results](https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2024-2025/Product_%26_Technology_OKRs#Key_Results), "gender" and "women's health" are mentioned in WE2.1.
- (Possibly other relevant examples. Feel free to suggest.) > [[ https://meta.wikimedia.org/wiki/Wiki99 | Wiki99 ]], [[ https://meta.wikimedia.org/wiki/Wikimedia_CEE_Spring_2024/Structure/International | CEE 2024 ]],
For the pages listed, it should be possible to mark them as collections just by adding the `<page-collection/>`tag. If there are technical complications or communities object, we can skip the particular case and consider alternatives.
Having several collections will be useful for users to switch between different collections, better differentiate the purpose of the "all collections" option, serve as an example for communities to adopt this feature and start to assess the impact of different types of collections (e.g., broad vs. narrower topic areas). This becomes more relevant as the translation dashboard becomes more accessible with the enablement of new entry points in more wikis (T371692).