aces
[module_manager] Suggest Refinements for usability
A few refinements in the module manager would make it easier to use.
Typically when setting up a new project, an admin will disable a dozen+ modules at the same time, and then over time enable a few more when ready, e.g. Data release, Data Dictionary, Data Query Tool.
a. A few modules don't make sense to disable:
- login
- API (also appears at the top of the alphabetical sort order in this data table)
- Module manager itself
- Config (it could be argued but... why)
- User Accounts - there's really no other way to manage this core functionality e.g. password reset, project affiliation.
b. Add in the Data table a "Menu" column so that you can sort/group modules by menu. Would also help to provide context on where they appear in the menus.
c. When disabling many modules at a time during project Setup, the SWAL2 alert popup (reload or continue) feels more disruptive/loud than it needs to be - e.g. If this alert popped up for every Config module change it would be jarring.
- Is it possible to add a
got it! don't show me this again todaycheckbox? - any SWAL2 config options so this alert is not so big/blaring? It's mostly there as a success/continue message.
- tweak language: Change "the interface" to "this page" ("the interface" sounds weird in a user-facing message)
still relevant:
a. A few modules don't make sense to disable:
login API (also appears at the top of the alphabetical sort order in this data table) Module manager itself Config (it could be argued but... why) User Accounts - there's really no other way to manage this core functionality e.g. password reset, project affiliation.
Would this be a good GSOC task for the next GSOC student?
Still relevant and yes, I think it could be a good first task for a GSOC.
