Is your feature request related to a problem? Please describe.
Our translated site content lags behind the English content. Currently we manually upload files into our CrowdIn project for translation.
Describe the solution you'd like
Describe alternatives you've considered
We've explored ditching CrowdIn & only using Github to manage translations (similar to how React & Vue manage their documentation translations) but for now we've decided to stick with CrowdIn given many of our translators are unfamiliar with Git.
Additional context
Hello Sam!
Let's set up a sync together this week 馃檪
sending you details in the email!
Hi @yavorysynka , you might have meant my email... :)
In any case, adding @samajammin to the loop is obviously useful and .
got it!
already sent you guys an email 馃檪
See for config example: https://github.com/Andrulko/ethereum-org-website/blob/dev/crowdin.yml
Thanks @Andrulko!
FYI, I'm hoping I'll have time to knock this out next week.
Regarding the config file, I think we can mostly follow that example above, although instead of specifying every single .md file to translate, I think we should default to adding all files, e.g.:
- source: /docs/**/*.md
ignore:
- /docs/%two_letters_code%/
translation: /docs/%two_letters_code%/**/%original_file_name%
Then explicitly adding "ignore" cases.
I think that will give us a more flexible approach vs. having to explicitly add every file. We want the default behavior to be to add any new file into CrowdIn.
I don't remember exactly why but I've made a decision to specify folder by folder o_O Probably, because I'm not a big fan of ignore :D
Your configuration should work fine too and whenever you add new folder to GitHub repo, it will be auto-synced with Crowdin.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
Most helpful comment
Hello Sam!
Let's set up a sync together this week 馃檪
sending you details in the email!