sui
sui copied to clipboard
MystenLabs
Explore generic contribution and localization of Sui website contents
What are the existing URLs containing the issue, if any? https://docs.sui.io/ https://sui.io/
How would you describe the issue? (What needs changing?) These are our top countries by user:
- United States
- China
- Russia
- Hong Kong
- United Kingdom
- Vietnam
Yet we offer our contents only in English. Meanwhile, we have community mods asking to translate our contents. We should eventually support more than the English language. There is precedent: https://ethereum.org/en/contributing/translation-program/ https://ethereum.org/en/contributing/translation-program/acknowledgements/
Where should this information land if new? (Learn, Build, Explore, Contribute.)
In language-specific subdirectories of each site.
What changes are needed to support this new feature or product? (A simple overview, detailed procedures?)
A whole new workflow.
Who is the audience for that information? (App developers, investors, creators, validators, someone else?)
Our users outside of English-first countries.
What precisely must they do with it? (Configure a new service? Process some output?)
Be more productive. Otherwise, each user must translate themselves and perhaps miss nuances we could resolve en masses.
@losamsel and @bhenhsi , we have someone offering to translate our Smart Contract and Tokenomics white papers in: https://github.com/MystenLabs/sui/issues/3412
They mention other but don't say which languages. Shall I ask them to try our web pages? Thanks!
More from Brian, community-submitted tutorials: https://ethereum.org/en/developers/tutorials/
Thanks, @bhenhsi !
Here is an example recent external contribution: https://medium.com/@megalodonear/sui-installing-node-step-by-step-guide-for-beginners-5c766ce94ab9
Find more in: https://github.com/MystenLabs/sui/issues/1065#issuecomment-1195752640
@Clay-Mysten and @bhenhsi see https://github.com/ethereum/ethereum-org-website/tree/dev/src/content/translations
@Clay-Mysten and @bhenhsi see https://github.com/ethereum/ethereum-org-website/tree/dev/src/content/translations
Thanks. LGTM for our plans long term.
I'm adding @randall-Mysten since he expressed a desire to edit the docs for localization. I believe some of this is underway. Randall, simply include the PRs here. Thanks!
@Clay-Mysten and @bhenhsi see https://github.com/ethereum/ethereum-org-website/tree/dev/src/content/translations
Have we already confirmed with a loc vendor that this is the appropriate structure to implement an integration?
@Clay-Mysten and @bhenhsi see https://github.com/ethereum/ethereum-org-website/tree/dev/src/content/translations
Have we already confirmed with a loc vendor that this is the appropriate structure to implement an integration?
What structure? The subdirectories for languages? That is a norm: https://stackoverflow.com/questions/8527306/deploying-net-satellite-assemblies-in-specific-folder https://stackoverflow.com/questions/4864984/separate-folder-for-language-files https://laravel.io/forum/02-23-2015-localization-load-files-from-subdirectories-at-resourceslanglocale
What did you have in mind?
I'm just trying to understand where things are in the process. There was some discussion of having community-based localization, but then we learned that there are vendors under consideration. I did not know whether this was to prepare for user-based or in response to a vendor discussion.
I am noting we have an offer from the person below to translate our contents from English and Ukrainian: Dmitry Bauer ([email protected])