New answers tagged information-architecture
1
The solution definitely depends on how close modules are related to each other from interface and architectural points of view.
If integrated module is just one item in application's main menu and is perceived by user as a part of whole application it's better to have its setting under one application's Settings section.
If module acts like a kind of plugin ...
0
In order to display overall settings as a top-level page/section, it's quiet useful to let users reach the sub-module settings within closest point to where user tasks exist.
By presenting a top-level settings page with a discrete section for each mentioned tabs above (like sub-modules, admin, configuration, etc.) it's obvious for users to think about where ...
1
I would certainly place settings close to he user tasks. This exposes the settings in small quantities at the exact time the user might be interested to change it. Going to the big settings section and doing mental gymnastics trying to link the settings to their features is extra effort that will make many users not use the settings.
Sysadmins do not have to ...
Top 50 recent answers are included
