Differences between staging and release

Just like staging is your test environment before releasing to production, so is it mine. And that means that there can be a difference between the 2 environments. The flow for translation is as follows:

I write some text in code.
GBIF communications proofread/change that in Crowdin
Once the english is in place it will appear for translations (that is why some labels are hidden and empty in e.g. spanish)
Once you have translated to e.g. spanish, then I will receive a pull request to bring the translation into the codebase.
Once I have agreed to do that then I have to deploy it for you to see it online. And I have to deploy to both staging and production if it is to show both places.

This is similar to GBIF.org where translation (automatically though) show up in our UAT (user acceptance testing) environment. But has to be explicitly released to go into production.

I typically merge translation updates into the test environment daily, but it can often take several days before going into production.

I can see why it is frustrating for you not knowing what it will look like. I will have to think before suggesting any alternatives

gbif / hp-colombian-biodiversity

Differences between staging and release #27