Keep the current locale visible in backend viewport at all times

[evertalbers]

Problem: If you have a long backend page and you scroll down, the current locale scrolls out of view. If the working locale has scrolled out of view and something (e.g. a phone call) has made the editor loose his focus*, there is a risk that he will get back to work and overwrite content, e.g. insert English content in a Dutch translation or v.v. and only notice this after saving.

Does this look familiar?

So my suggestion is to discretely show the current locale in the viewport permanently, in a corner of the off-white area somewhere, not in the header since it is related to the content.

Alternatively, less subtle ways to do this would be to smack a position:sticky on the Current Locale- card, or attach a flag to the mouse/cursor.

*) https://www.youtube.com/watch?v=-kieJaT9EIA

[Halopend]

Not a terrible idea as it certainly happened to me more than once. That said, the scarier part is if you make changes in one tab and then switch back to another tab without refreshing you can overwrite sections since the entire contents of the page gets submitted (including sections that might be on both sides) which haven’t been “updated” like they may have been in another tab.

That’s a very difficult problem to solve though and generally falls more into the workflow side of things.

I think the ability to copy content to other languages to allow content editors to overwrite in place would solve a large portion of the currently required workflow that leads to this issue cropping up more often….. but the biggest issue to solve is how to handle collections (as exact parity between lanaguages isn’t always guaranteed…. And these sections can be dynamic in length).

Something that lets you copy once and then maintain the changes from there is likely a “good enough” solution since most companies handle translations at the end after one language is “locked in” and verified to be perfect…. But it’s something to think about.