In theory, the only parts of the backend code where you need localization is the settings declaration and standardized data (ActivityPub, RSS, ...).Here we need to get english strings from the translation key.
There is a specific "Hugo shortcodes" you can use to display an application string.Saying you want to display the name of the button "open_chat_new_window", you can use this in the documentation markdown file:
If a string contains a link, you can change it for the correct link in the translated language.For example, for a link to this documentation, you can add the language code in the url.
The tool I use to handle translations for the documentation can have strange behaviours. When I add sentences that looks like other existing sentences, it sometimes copies existing translations. So, when you have translations marked as "to check", please make sure it doesn't copy a string that has nothing to do with the english one before validating.
If you are now sure about the context of a string, you can check the string location in the weblate's right pane, and open the corresponding documentation page.For example, for a string located in the file `support/documentation/content/en/documentation/user/streamers.md`, the corresponding url is `https://livingston.frama.io/peertube-plugin-livechat/documentation/user/streamers/`.
