Documentation Translations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
tldr; documentation seems stable enough for us to consider supporting translations and a process to automate it and have a light review process
In addition to the tldr, there are very large communities interested in PyScript and language is actually a barrier. They'd receive great value from a local translation of our documentation. The risks we identified in the past, when having this conversation before, have mainly been solved and the project is mature enough for us to bring this topic back. In addition to that, LLMs are actually not bad at translating text/code with good contextual awareness.
With all of that in mind, let's do it!
/cc @ntoll
Contributor guide
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
The issue proposes translating the documentation, automating the process, and adding light review, but names no files, tests, or entry points. Start by locating the current documentation and the earlier translation discussion, then define explicit supported languages, automation, review, and completion criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, internationalization, localization
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100