Dokumentacija

Opće informacije

Always inform the community before working (by creating a new issue, or commenting an existing one). This is to avoid that two persons are working on the same thing, and prevent conflicts.

Documentation work has to be merged in the main branch.

The documentation source code is in the support/documentation/content folder.

The documentation is generated using Hugo. You have to install it on your computer if you want to preview your work.

The minimum required version for Hugo is 0.121.0. It was tested using version 0.132.2.

The used theme is hugo-theme-relearn. You should read its documentation before starting editing the documentation.

When a new plugin version is released, or when documentation is updated, plugin maintainers will merge the main branch to the documentation branch. This will trigger github and gitlab pipelines, and update published documentation.

Prijevodi

Glavni jezik je engleski (kod: en).

Mapa support/documentation/content/en sadrži datoteke dokumentacije samo na engleskom jeziku.

Dokumentacija se prevodi pomoću Weblate platforme (pogledaj Prevođenje dokumentacije). Za to koristimo alat po4a, što ćemo kasnije vidjeti na ovoj stranici.

Dodaj novi jezik

U datoteci support/documentation/config.tomlkopiraj i izmjeni odjeljak [Languages.fr].

Ako prijevodi nisu potpuni, nedostajući izrazi će se prikazati na engleskom jeziku.

Pregled

Za pregledavanje tvojih izmjena pokreni naredbu:

hugo serve -s support/documentation/

Then open your browser on the address http://localhost:1313/peertube-plugin-livechat/. This page will automatically refresh on each modification.

Update localization files and generate documentation translations

For now, you only have the english version. To update documentation strings, and generate translations, you have to run the doc-translate.sh script.

Za to moraš imati po4a (verzija ≥ 0.69) na tvom računalu.

To handle translations, just do:

npm run doc:translate

You can then preview the result using hugo serve -s support/documentation/, and using the language selector.

Piši dokumentaciju

Uredi engleske datoteke u mapi support/documentation/content/en.

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.

Za korištenje izraza aplikacije možeš koristiti kratki kod livechat_label. Pogledaj ovdje: Prijevod dokumentacije.

It is possible to prevent a file from beeing translating, using livechatnotranslation: true in the Yaml Font Matter section. See here: 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.

To facilitate translators work, avoid making too long paragraphs.

For now, it is not possible to use Markdown tables: the translation tools will break them.

When a new feature is released, you can use the livechat_version_notice short code to display an infobox with the version with which the features is available. This short code takes the version number as parameter. Here is an example:

What if I can’t use hugo and/or po4a?

Just edit english markdown files, and specify that you can’t build translations when you make your Pull Request.

Publication

Publishing the documentation is automatic, as soon as the changes are merged into the documentation branch.