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
Thanks for the info. I will give it a try...
How often is the settings.php loaded.
I use Lando (a wrapper for docker) and find settings changes happen straight away
How often is the settings.php loaded.
You might need to add a Relationship in the View to Flags. Or there might be a setting on the content type. I can't recall for certain but I think it's possible.
No Flag fields in Views