Then, before commiting, always run `npm run doc:translate`, so that changes in english files can be propagated to the `support/documentation/po/livechat.en.pot` file.
Youcan use the `livechat_label` short code to use application strings.See here: [Documentation translation](/peertube-plugin-livechat/contributing/translate/#documentation-translation).
It is possible to prevent a file from beeing translating, using `livechatnotranslation: true` in the Yaml Font Matter section.See here: [Documentation translation](/peertube-plugin-livechat/contributing/translate/#documentation-translation).
Please use the `livechatnotranslation` option for technical documentation.We don't want technical documentation to be translated, to avoid issues because of a wrong translation.
There may be links to this documentation elsewhere onthe web.Try notto changethe urls of the documentation pages.Or at the very least, put links to the new location onthe previous url.
When a new feature is released, youcan use the `livechat_version_notice` short code to display an infobox withthe version with which the features is available.This short code takes the version number as parameter.Here is an example:
You don't need to know how to code to start contributing to this plugin! Other contributions are very valuable too, among which: youcan test the software and report bugs, youcan give feedback, features that you are interested in, user interface, design, ...