New answers tagged cms
You can combine options 2 and 3, to link the scroll position and which tab appears selected. As in the Change active tab depending on scroll position answer. Or you can use Miller columns as in Finder on Mac.
Your best bet is Option 1. Let me address your concerns: -Separate page/form for each plugin seems pretty heavy Unless you can know for sure how many settings each plugin will have, giving an entire page seems to be the most flexible option. Furthermore, it creates a separation in the user's brain that seems useful: There is no interaction between each ...
It all depends on the number of things you might need to account for (scalability). Another way to score this is based on efficiency: Option 1 users can access everything with just one mouse-click. Nothing is hidden. Option 2 users need to make 1 mouse-click and scroll the page to view everything. Some things are hidden until you scroll. Option 3 users ...
I think collapsible section on the right may be better. It makes it easier to read and see the different sections. Tabs are also limited in size and width. With a collapsible section you have more space for the title and purpose of each plugin. It can grow vertically dynamically.
A fourth option would be an extra settings dialog for every plugin. But this would certainly be the worst option because it will separate the options. Basically you have to take three numbers into account: number of NPCs number of MODs number of options per NPC/MOD Depending on what number is more likely to grow you will have to decide between your ...
Although I totally get the position you are in, instead of trying to "fix" the old implementation, maybe you should consider starting from the beginning of the UX process, particularly gaining an understanding of what particular types of users (personas) most want to get out of the system (red routes). Maybe working on information architecture. Do some ...
Top 50 recent answers are included