I will be building an application to create simple websites. The backend user will be able to add, delete, and modify the following:
- Menus (can be added to pages)
- Widgets (can be added to pages)
The backend application will have a main menu with links for each of the above. Traditionally, I've made the links go to a list page showing a list of each (i.e. a list of users, a list of pages, etc), and each row would also have some extra key information as well as a delete button. The page would also have a general Add New button. Upon clicking a given name in the list, a detail page is shown which displays all the information for the given record and gives the user the ability to modify the record. The detail page typically also has a Delete button as well as a Add New button.
For this application, the expect number of rows in the list pages is expected to be fairly small (ranging from 5 to 20), sorting and filtering is not required, and I am contemplating getting rid of the list pages, and having the main menu go directly to the associated detail page. Each detail page would have a Go To button which will open a dialog listing all the records of the given type (i.e. a list of users), and upon clicking one, they go to the detail page for that record. Each detail page will have a Delete button, and either an Add New button or instead, the Go To dialog will include a Create New button (please comment if you have opinions on this).
From a user experience prospective, what are the pros and cons of using list pages verse making these lists only accessible through a dialog from each detail page?