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.
Try to autodetect colors from user's current theme.<br> When this setting isenabled, the plugin tries to auto-detect colors to apply to the chat theme.<br> If thisisnot correctly working for some of your Peertube theme, youcan disable this option. Youcan report the bug onthe official <a href="https://github.com/JohnXLivingston/peertube-plugin-livechat/issues" target="_blank"> issue tracker </a>. Don't forget to specify which theme isnot working.
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: