You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Write a comment in this issue like I am taking page-name.md
Create fork of this repo
Be sure that you are making a translation based on lang-ru branch
Create a pull request to this repo with name [WIP] page-name.md even if/while translation is not completed yet (for everyone to know that you are really working on it, or if you will leave it - someone could use your starting point and continue, so your work would not be lost in any case)
Refer to previous docs version translation, maybe the docs article you are working on was already translated and you can find some text parts.
When you finish a translation rename a pull request and repo [WIP] prefix
Be sure that your branch is up-to-date with latest state of this repo's lang-ru and pull request could be merged without conflicts
Make a comment here like Finished page-name.md <link to pull request>
Someone will review your translation and I'll accept a pull request
Review
Even if you are not very good in English to translate by yourself, or have no time etc. You still can contribute.
If you see a 🙈 review needed label on page. It means that translation is completed, but some native speaker should review it in Russian. To track down bad wording, mistypes or anything that "looks weird" for a Russian native-speaker. If you found something - ideally make s fix pull request, or at least create an issue with back links to "error" lines.
If you have reviewed some doc and it looks fine for you - write here in comments to mark it as done 👍
Priorities
Pages are ordered in the table as they are ordered in docs, so it is supposed to translate them in the same order. You are free to select any page, but it's better to go one-by-one in the list
@simplesmiler Hard question. I tend to consider everything as translation from the scratch.
Just consider that some parts are already translated and while working on 1.0 docs, for example "computed.md" refer to 0.12's "computed.md" - maybe some parts could be "reused". But as a general rule it seems to be hard (maybe I am wrong, let's start and then we'll see).
Updated lang-ru branch with actual docs state (not translated).
Previous progress transferred to [email protected].
In nearest days hope to bring back CircleCI for automatic docs site rebuilding. And to transfer back all Hexo parser features - like markdown plugin with abbr support etc. To try to push it to main Vue docs repo.
How to help with translation
I am taking page-name.md
lang-ru
branch[WIP] page-name.md
even if/while translation is not completed yet (for everyone to know that you are really working on it, or if you will leave it - someone could use your starting point and continue, so your work would not be lost in any case)[WIP]
prefixlang-ru
and pull request could be merged without conflictsFinished page-name.md <link to pull request>
Review
Even if you are not very good in English to translate by yourself, or have no time etc. You still can contribute.
If you see a 🙈
review needed
label on page. It means that translation is completed, but some native speaker should review it in Russian. To track down bad wording, mistypes or anything that "looks weird" for a Russian native-speaker. If you found something - ideally make s fix pull request, or at least create an issue with back links to "error" lines.If you have reviewed some doc and it looks fine for you - write here in comments to mark it as
done
👍Priorities
Pages are ordered in the table as they are ordered in docs, so it is supposed to translate them in the same order. You are free to select any page, but it's better to go one-by-one in the list
/source/guide
/source/api
/source/examples
/themes/vue/layout/*.ejs
Setup gh-pages site for 1.0 http://vuejs-ru.github.io/vuejs.org/
@iJackUA 🚧 work in progress
Legend
The text was updated successfully, but these errors were encountered: