LibreSign / LibreSign/documentation
Internationalization (L10N) Support for the Documentation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 6
- Avg merge
- 19h 12m
- Merged PRs (30d)
- 1
Description
Currently, all documentation is written in English. To make it more accessible, it would be beneficial to provide translations in other languages.
The main Nextcloud documentation uses Transifex] for localization and can serve as a good implementation reference.
This issue can be broken down into the following tasks:
- Add i18n/L10N support to this repository using Sphinx's internationalization workflow
- Integrate with Transifex to manage community translations
- Automate pushing and pulling translation files from Transifex (e.g., via GitHub Actions)
This is a good first issue for someone who wants to make their first contribution. Feel free to ask questions in the comments if you need help!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading Sphinx's internationalization workflow and the main Nextcloud documentation's Transifex setup. Then map how this repository builds documentation and where GitHub Actions can automate translation file pushes and pulls; done means localized documentation support, Transifex integration, and working automation for both directions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, documentation, localization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100