[wp-meta] [Making WordPress.org] #7769: Live-Preview: load Playground in actual language

[Making WordPress.org]

#7769: Live-Preview: load Playground in actual language
------------------------------+--------------------
 Reporter:  threadi           |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 The path from international WordPress plugin sites to the Playground is
 currently still somewhat confusing. If you click on a live preview button
 on https://de.wordpress.org, for example, you always end up in an English
 environment - not the German one.

 Currently, the plugin-directory plugin calls this URL from the Playground,
 regardless of which language is actually used:

 {{{https://playground.wordpress.net/?plugin=%s&login=1&url=%s}}}

 Source:
 https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
 /wp-content/plugins/plugin-directory/class-template.php?rev=12931#L734

 -----------

 I have 3 ideas for optimizing this:

 a) **Call up the playground with a language parameter at the above
 mentioned source.** I have already opened an issue in the Playground group
 on github, but I think it might be too complex to parameterize a JSON
 file: https://github.com/WordPress/wordpress-playground/issues/1703 - it
 would also not be as flexible as the following idea.

 b) **Introduction of language-specific blueprints.json at wordpress.org.**
 Each plugin developer could provide these separately and thus ensure a
 conversion themselves. There are certainly plugins that are fixed to a
 region of the world with a specific language, which would then have
 everything in their hands. They could then also provide individual
 language-specific content that they define in their own language-specific
 blueprint.json (which would not be possible with idea a)). This would also
 be analogous to the procedure with screenshots, which can also be
 language-specific. I could imagine storing the language-specific
 blueprints.json in subdirectories in the SVN:


 {{{
 /assets/blueprints/blueprint.json
 /assets/blueprints/en/blueprint.json
 /assets/blueprints/es/blueprint.json
 /assets/blueprints/fr/blueprint.json
 }}}


 If this were basically possible, one would only have to define which
 language abbreviations are allowed ("de_AT", "de_CH-informal" ..).

 c) **wordpress.org could generate a language-specific file from the basic
 blueprint.json** and pass it on to the Playgroud. The challenge here is
 that such files must also be stored somewhere and somehow.

 -----------

 At the moment I think that b) would be the best option. I would be happy
 to read the opinions of those who are most familiar with the technology
 involved at wordpress.org :)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7769>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org