-
Notifications
You must be signed in to change notification settings - Fork 264
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
Make playground translation ready #1991
Comments
Playground isn't translatable today, but it would be wonderful if we could get there. Here are a few thoughts on how we could get there.
|
Looping in @akirk @amieiro – how would you go about making Playground translatable with the existing WordPress infrastructure? Technically, we're talking about a React app. One idea is packaging the code as a WordPress plugin. It's not ideal, as there would be no actual way to use that plugin, but it's something. Do you have any other ideas ? |
In the Meta project we have a similar situation: the Openverse project. This project uses Nuxt.js/Vue.js. They have the English strings in a JSON file. They use these strings in the frontend to be able to translate them. E.g., the
We could have a similar situation:
|
Playground heavily uses WordPress components. We should also consider how to make these strings translatable. |
I am at a Spanish WordCamp and we've been extensively using Playground for contributor day and workshops. We have the translation team here and we were wondering if the Playground interfaces were translatable. I think when you change the WP language the Playground interface should update to the selected language if a translation is available for it.
If you make playground translation ready, you already have translators waiting on it to translate into Spanish at least :)
The text was updated successfully, but these errors were encountered: