Repository: mozilla/pontoon

Issue:
Provide new contributors with guidelines before adding their first suggestion in a locale
*This issue was created automatically by a [script](https://github.com/mathjazz/bugzilla2github/).*
## [Bug 1726881](https://bugzilla.mozilla.org/show_bug.cgi?id=1726881)
Bug Reporter: @flodolo
CC:   @Delphine, @mathjazz, reza.hbi@gmail.com

Right now, a new contributor can start translating without looking at style guides, or info on the locale (which is not exactly visible).

It would be valuable for locale managers to be able to set up a message, explaining what the workflow for the locale is, if there are style guides, etc.

For example:
- Locale managers for `it` set up this type of information, and enable this INTRO feature for their locale (maybe it's enabled automatically if the information is provided). The message should allow links, potentially we could display it as a subsection of the locale INFO tab.
- When users are trying to contribute for the first time to a specific locale, if the INTRO feature is enabled, we display a message pointing the user to the locale INFO tab (we could also hint at the fact that someone needs to approve their suggestion). The user can dismiss the notification, and it won't be displayed again.


Discussion:
Comment Author: @mathjazz

We've talked a lot about improving onboarding in the past, including at the recent [workshops](https://docs.google.com/document/d/1hsUgHS8in90ba6GoGXai-7PfUR__JmhZeeouj2c-QK4/edit#), and I'd be happy to finally take action.

Before working on specific tasks, I suggest we learn more about the actual pain points, clarify value proposition, and outline plan to address onboarding more holisticaly.


Comment Author: @Delphine

Something in relation to this that came out of the workshops to improve onboarding is:
sending out a "welcome"-specific email, that would also be sent to CCed managers/translators. Related to flod's intial Description, that could include welcoming them, directing them to our docs, explaining how to get in touch with the managers, and clarify what will happen with their suggestions. This let's translators/managers know as well that someone is new, and makes the new person feel included - and gives guidelines for contribution



Resolving patch:
diff --git a/pontoon/api/schema.py b/pontoon/api/schema.py
--- a/pontoon/api/schema.py
+++ b/pontoon/api/schema.py
@@ -89,6 +89,7 @@ class Meta:
             "plural_rule",
             "script",
             "population",
+            "team_description",
             "total_strings",
             "approved_strings",
             "pretranslated_strings",
diff --git a/pontoon/base/views.py b/pontoon/base/views.py
--- a/pontoon/base/views.py
+++ b/pontoon/base/views.py
@@ -865,6 +865,9 @@ def user_data(request):
             "display_name": user.display_name,
             "name_or_email": user.name_or_email,
             "username": user.username,
+            "contributor_for_locales": list(
+                user.translation_set.values_list("locale__code", flat=True).distinct()
+            ),
             "manager_for_locales": list(
                 user.managed_locales.values_list("code", flat=True)
             ),


Test patch: