This proposal is a larger suggestion that is out of scope for the Community Tech team. Participants are welcome to vote on it, but please note that regardless of popularity, there is no guarantee this proposal will be implemented. Supporting the idea helps communicate its urgency to the broader movement.
Problem: MediaWiki hasn’t been designed to make dictionaries or thesauri, to manage a distributed multilingual content, to interface lexicographical and semantics data and “sentence-plain” contents. The only improvement made to fix that point is Cognate extension, whereas many ones are needed so Wiktionaries can address their goals.
Proposed solution: Create a dedicated team, including a project manager to coordinate these efforts, a product owner in liaison with communities, a UI/UX engineer to design some propositions and to test them with readers and editors, developers to implement chosen improvements, a communication manager to cover this work and to assist the transformation of practices.
Who would benefit: All Wiktionary editors and readers, from all language communities.
Clearly out of scope of Community Tech team. However, keeping only UX side, Community Tech could work on skin improvements and JavaScript features to redesign Wiktionary reading (facilitate browsing through sections — languages and subsections). The problem it would fix would be “It is hard for Wiktionary readers to find the information they look for in right language when they are on the right page.” --Pols12 (talk) 20:24, 11 January 2022 (UTC)[reply]
Thanks for the translation. I'll keep it as such because the need is clear and broader than a reading issue. Moreover, your proposal is neat, it could be another wish. Noé (talk) 10:50, 12 January 2022 (UTC)[reply]
Support I've almost never edited Wiktionary, but I've increasingly been using it lately and it's clear that while it is a platform with an astonishing amount of content, it's built and run on tools that were not designed for it. Uanfala (talk) 22:54, 9 February 2022 (UTC)[reply]