During the local WordPress meetup last week, there was also a TYPO3 presentation. They have a UI where content is being translated to other languages while having the original text displayed next to it:
I realize that we have not yet started working on multilingual support, but there's nothing wrong with planning ahead
I think that this side-by-side approach is way better than the Drupal way of prepopulating the fields with the text of the original language:
That way, when translating content in Drupal, people either overwrite the original text as they are translating, or they start translating below/above it and delete the original text once they are done. Either way, there are UX flaws: if you overwrite the original text, there is no easy way to do a final review - if you keep the original language text around, there's a lot of scrolling up and down.
I thought that perhaps in Backdrop we can have something similar implemented as a two-column layout shipped with core that it is specifically designed for content translation. It would have the content edit form on one column and the preview of the original language on the other side. Perhaps both sides could have the content in edit mode (sometimes you need to adapt the original language text in order to make it easier to be translated in other languages). Perhaps it would also be useful to have a drop-down menu on both sides that would allow selecting which language is on which side. Not entirely sure how we could make this work (or whether it would be possible at all), but on sites with more than two languages, the language drop-down menus could work in an AJAXy way, loading the content edit form of the selected language "on the fly" without page reloads.
Because this would be a layout, people would be able to customize other things as they see fit. For example, changing the layout template to one with 3 columns so that they can be translating/previewing three languages at the same time.
This is just an idea of how things could work UI-wise. Not sure if any of this is possible with the current underlying "infrastructure".
Recent comments
Thanks! The site was on PHP 7.0. With assistance from my hosting provider, I updated to PHP 7.4 and now I have access to the site again. No database re-import required.
Locked out of site after updating modules
Thank you very much. I will follow your advice.
Locked out of site after updating modules
The best you can do is test and report. If you find a contrib that doesn't work in php 8.3, create an issue in its queue so it gets fixed. In my experience, I've found that 7.4 is safest...
Locked out of site after updating modules