I thought of this idea while filing #5948.
It would be cool if we could inject a "mini" modules form in the "Regional and language" page in admin/config/regional, so that people can enable these modules without having to navigate elsewhere in the admin UI and then return back to the page where they were expecting to find the relevant options. Kinda what we are doing with the permissions matrices we are injecting in other places.
I have a few ideas about the UI, but if people believe that the interface could get overwhelming and cluttered, then we could hide these options in a collapsed fieldset. ...OR simply stick with the help text and link from #5948 and shoot this request down.
In general though, perhaps we should be shifting from the developer-centric notion of "modules" into features or functionality instead. The modules listing page and the project browser are cool and we should still keep them, but what I am trying to explore is a way for some modules to be options in various places where it makes sense from a non-Drupal/non-Backdrop/non-developer person.
Recent comments
There is a Drupal 7 contrib module that "lets the administrator see all administration pages in her preferred language" and which could be ported to Backdrop: https://www.drupal.org/project/...
Allow admin to select admin language seperate from front end language (multilingual)
@stpaultim – You're right: my approach affects also the main menu. I guess, because menus are also considered as user interface (not as content). @findlabnet – If I didn't miss anything,...
Allow admin to select admin language seperate from front end language (multilingual)
Go to the account edit of the desired user. On the horizontal tab below "Region and Language," select "English" or another language. WFM.
Allow admin to select admin language seperate from front end language (multilingual)