tolgee-platform
tolgee-platform copied to clipboard
tolgee
Feature suggestion: Facility to define status workflows
Hey, I've been checking out the project and it's great! The UI is easy to use and I'm going to take a look at the integration with Vue and i18n next.
The main thing I noticed was the lack of control over the translation workflow. The context I'm coming from (international Edtech) is slightly different to standard app interface localization.
A lot of content organized as modules needs to be both localized or translated and go through multiple verification stages. I saw that permission enhancements are on the roadmap. I think it make sense to consider status and workflow management while working on permissions since it works best when stages are defined by access rules.
Of course it doesn't make sense to have complex workflows for every element. However if translation keys could be organized into user defined collections then the status and workflow stages could be applied to collections of translation keys.
Perhaps this could be defined from the frontend or even programmatically from the structure of the translation keys.
Interested to see what you think.
Hey! Would you be open to have a quick call with me? We are actually considering options now and it would be nice to know more about your proposal and your use case.
This issue is stale because it has been open for 30 days with no activity.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Is this still on the roadmap?
We also need some custom workflows, but nothing too fancy. We want: 🟡 Translated -> 🟣 Reviewed, but has Typographic Error OR 🟣 Reviewed, but Incorrect Translation -> 🟢 Reviewed
This makes the most sense as a status because then it's per translation. Tags only apply at the key level so it's much harder to filter keys down to a list like "Show me all reviewed translations that had a typographic or syntax error for sw-KE only"
These custom statuses can self identify which "real" status they should be handled as- my custom status should act as a reviewed status or a translated status or an outdated status... don't need to add custom logic to the backend (yet) to get significant value from just having a few different label options for filtering.
