doc the weblate workflow for Volto (#1957)

* doc the weblate workflow for Volto

* Update docs/i18n-l10n/contributing-translations.md

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/i18n-l10n/contributing-translations.md

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/i18n-l10n/contributing-translations.md

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/i18n-l10n/contributing-translations.md

---------

Co-authored-by: Steve Piercy <[email protected]>

Author: erral

docs/i18n-l10n/contributing-translations.md

@@ -112,6 +112,20 @@ When you save a translation, then it is committed on a branch used only for tran
 Maintainers will periodically review the pull request that Weblate creates automatically, and merge it.
 
 
+### Wewblate workflow in Volto
+
+For all pull requests, Volto's CI checks for both the presence of a change log entry and that the `.po` files used in translations comply with a standard format.
+
+Weblate doesn't create a change log entry, and its `.po` file style guide does not match Volto's.
+This means that a Volto Team member has to perform the following tasks to merge the changes coming from Weblate.
+
+- Checkout the `translations-18.x.x` branch from the Volto repository.
+- Add a change log file in the `packages/volto/news` folder.
+- Run `make i18n` to reformat the `.po` files.
+- Commit and push the changes to GitHub.
+- When all CI checks succeed, then merge the pull request.
+
+
 (contributing-plone-core-translations-support-label)=
 
 ## Support