-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Crowdin #51
base: master
Are you sure you want to change the base?
Add Crowdin #51
Conversation
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Signed-off-by: Joshua Castle <[email protected]>
Maybe you can use Crowdin Webhooks to trigger Github Actions to sync translations with Crowdin. This way, you can avoid syncing on every commit. |
The sync time is negligible (under 20 seconds). The major build time issue is the fact that docusuarus must build each locale separately. I could probably shave off 30-50% with caching og images, but I think I could achieve the largest savings by building all languages separately in a matrix, and then combining the builds after the fact. I just need to see if docuusaurus sites built to an individual locale can be successfully combined. |
Closes #9.
Still need to optimize deployment strategy as currently it takes about 20 minutes for 10 locales. I am considering either doing a GH actions matrix to build various locales in parallel, adding caching for web thumbnail generation, or both.
See https://geyser.kastle.dev/. Select "Crowdin" from the locale menu to demo in-context translation.