OrchardCore
OrchardCore copied to clipboard
OrchardCMS
Move all settings menu items under Configuration > Settings menu
Is your feature request related to a problem? Please describe.
Currently, site settings provided by modules are scattered on the menu in many places. Form user experience, it would be nice to place all settings under one dedicated location on the menu for easy of access and quickly know where are all the settings located.
Also, the text style on the menu items isn’t unified.
Describe the solution you'd like
Move any site setting or configurations under the “Configuration > Settings” menu
Additionally, we may want to unify the naming by using a common style. Either a title case or sentence case for every menu item. I think using sentence style will look good on the menu item as per the recommendation here
Here is how the new menu structure may look like
Configuration > Settings > Search Configuration > Settings > Security > User login Configuration > Settings > Security > User change email Configuration > Settings > Security > User registration Configuration > Settings > Security > User reset password Configuration > Settings > Security > Security header Configuration > Settings > Security > HTTPS Configuration > Settings > Security > CORS Configuration > Settings > Security > reCaptcha Configuration > Settings > Security > OpenID Connect > Authentication client Configuration > Settings > Security > OpenID Connect > Authorization server Configuration > Settings > Security > OpenID Connect > Token validation Configuration > Settings > Security > OpenID Connect > Management Configuration > Settings > Security > Authentication > Facebook Configuration > Settings > Security > Authentication > Twitter Configuration > Settings > Security > Authentication > GitHub Configuration > Settings > Security > Authentication > Google Configuration > Settings > Security > Authentication > Microsoft Configuration > Settings > Security > Authentication > Azure Active Directory
Needs some discussion, the current menu organization was discussed and designed this way.
@sebastienros sounds good. I just think centralizing settings related items into one place will make the UI easier to navigate. For anyone looking for settings, they are always in the same place.
I kind of agree with him that "Security --> User / Roles" should be separated from the "Configuration --> Security" settings. Makes sense to me to be able to quickly find an admin UI to manage users/roles but having all the settings in there is not necessary. We don't need to access these settings most of the time.
IMHO - end user looking Configuration menu they tend to think configuring site in terms of general setting related to the site and Setting of each vertical functional group to have its own settings i.e. what we have today Security -> Settings
Also having more than 2 level of menus are annoying and not good UI experience
Also having more than 2 level of menus are annoying and not good UI experience
Could you please add anything related to UI/UX to the related issue to mak it easier for tracking
@ns8482e I agree with you also. Maybe that's the compromise that has been done so that we don't have too many levels of sub-menus. Either way, I don't think it is currently causing any issue as everything is accessible.
@Skrypt @ns8482e may be we can create a new menu in the root called "Settings" which will be under "Configurations" or drop "Settings" level altogether and list all settings directly under "Configurations"
I think it is a MUCH better user experience to group all settings/configurations under the same node. IMO, placing all settings in one place removes the guessing from the user experience. Settings are not always accessed and should be a second class citizens but should be grouped.
Let's find the meeting where we discussed about Configuration vs Setting menu items. And when these items were first introduced.