Provide context to translators during translation of GitLab product UI strings on Crowdin
For a translator, having context (visual or explanatory) is important for ensuring accurate translation.
The goal of this issue is to provide to translators of GitLab product UI the necessary context, by offering to translators the research tools that can be used to find context, so translators can understand where a certain UI label appears, what it means, etc.
Currently, the only source of context for translators (except some context that can be derived from [the descriptive namespaces](https://docs.gitlab.com/ee/development/i18n/externalization.html#namespaces)) is the text that the translators see
1. **i**n the Crowdin translation interface, or
2. in the [.pot](https://gitlab.com/gitlab-org/gitlab/-/blob/master/locale/gitlab.pot) file. \[screenshots below\].
Both resources are simply a listing of text strings. Without knowing what the text means or where the text is used, it is very hard for translators to understand the intent and provide accurate translation.
1.
{width="411" height="377"}
2.
## {width="408" height="565"}
epic