Translation Project Sorting Ideas

We’ve been collecting some ideas for sorting all of the projects that are being imported (themes and plugins). I want to collect some of the ideas here, along with my thoughts on them. If you have other ideas, we’d love to hear them!

  • Prioritizing by popularity: Projects could be organized by how popular they are, that is, how many users and/or downloads they have. For translators, the projects that are used the most by users are often considered the most important.
  • Prioritizing by fewest strings remaining: If a project is almost complete – e.g., just a few strings away – it can be considered higher priority. By enabling this option, we’d give translators a way to complete more projects faster. Personally, I think this is better than doing by percentage because 1 string remaining in a project of 10 is fewer than 10 strings remaining in a project of 1000, despite the latter being a lower percentage.
  • Prioritize by permissions: If a translator is the translation editor for a specific project – or a few specific projects – we could show those projects first, since they have permission to approve translations for that project.
  • “Hide” fully translated projects: If a project is fully translated and strings are fully approved, we could “hide” those projects or at least put them at the very bottom of the list. For themes and plugins, this will put them on the last page of results. Searching will still find them, of course.
  • Starring or Favoriting: Everyone has one or two themes/plugins that they really love and want to see available in their language. Giving translators the ability to “favorite” a project and have it raise to the top would make it easier to keep track of new strings in their favorite projects. We could even create a new “tab” for “Favorites” that could be the default if a translator has favorites.
  • Sort by waiting: Translation editors should be able to see which projects have waiting strings so they can approve them. Within this view, we should probably prioritize projects based on some of the ideas above.
  • Improved search: Translators should be able to search by author name (theme or pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party) and see a list of their projects, for example.
  • Consider “alerting” when changing a translation: It’s hard to explain this, but if I, as a translation editor, change the translation of “gallery” in one project, GlotPress should alert me to the fact that other projects have a translation of “gallery” that is the “old one” and possibly even offer to update all projects with the new translation.

The ideas above are just that: ideas. We may not implement any of them or all of them. But it’s important to list them and think through how we can improve the translation experience.

What other ideas do people have on sorting, prioritizing, and generally improving the translation experience of The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization.

#i18n, #translations