Feature documentation
Arabic translation / localization of the webpack.js.org documentation.
we are a small group of 4-5 native Arabic speakers interested in contributing an Arabic translation for webpack.js.org.
we noticed that the README still points contributors to the translation branch:
https://github.com/webpack/webpack.js.org/tree/translation however, that branch appears to be very old compared to the current main branch, and the current documentation content is now in .mdx files under src/content.
before we start translating or opening pull requests, we would like to ask what contribution path the webpack documentation team prefers for a new Arabic translation.
Author(s)
Suggested contributors to the Arabic translation:
N/A for feature authors, since this is a documentation translation proposal rather than documentation for a newly implemented webpack feature.
Additional information
Our proposed approach:
- start from the current
main branch, not from the old translation branch.
- begin with a small proof of concept instead of a large translation PR.
- translate only 2-3 important pages first, for example:
src/content/guides/installation.mdxsrc/content/guides/getting-started.mdxsrc/content/concepts/index.mdx
- we'll keep all code examples, package names, option names, links, and MDX structure unchanged.
- use a shared Arabic glossary to keep technical terminology consistent.
- submit small pull requests for easier review. (also look at the questions bellow)
- since maintainers may not be Arabic speakers (ig), so each translation PR will be reviewed internally by at least one separate native Arabic speaker before submission.
we are willing to maintain the Arabic translation over time, not only submit a one-time bulk translation.
[x] I am willing to work on this issue and submit a pull request.
Questions:
- should Arabic translation work to be in this repository ? or in a separate repository, or under a separate domain/subdomain?
- should all translation work be based on the current
main branch?
- would the team accept a small Arabic proof-of-concept PR before a wider translation effort?
- is there a preferred structure or workflow for new language translations?
- are there maintainers or reviewers we should coordinate with before starting?
Feature documentation
Arabic translation / localization of the webpack.js.org documentation.
we are a small group of 4-5 native Arabic speakers interested in contributing an Arabic translation for webpack.js.org.
we noticed that the README still points contributors to the
translationbranch:https://github.com/webpack/webpack.js.org/tree/translation however, that branch appears to be very old compared to the current
mainbranch, and the current documentation content is now in.mdxfiles undersrc/content.before we start translating or opening pull requests, we would like to ask what contribution path the webpack documentation team prefers for a new Arabic translation.
Author(s)
Suggested contributors to the Arabic translation:
N/A for feature authors, since this is a documentation translation proposal rather than documentation for a newly implemented webpack feature.
Additional information
Our proposed approach:
mainbranch, not from the oldtranslationbranch.src/content/guides/installation.mdxsrc/content/guides/getting-started.mdxsrc/content/concepts/index.mdxwe are willing to maintain the Arabic translation over time, not only submit a one-time bulk translation.
[x] I am willing to work on this issue and submit a pull request.
Questions:
mainbranch?