adapt_authoring
adapt_authoring copied to clipboard
Remove sidebar
trafficstars
As per the UI designs v3.
If we look at the types of action which are common across pages in the tool (and therefore things that need to be included in a sidebar), we have a very small group:
| Type | Description | Example |
|---|---|---|
| Action buttons | Buttons which perform a primary action on the page | Save/Preview/Upload plugin |
| Link buttons | Buttons which navigate away from the current page. | Project settings, Menu picker |
| View actions | Anything which modifies the 'view' of the current page (i.e. somehow changes what's displayed). This one's a bit broader, but can basically be split into two sub-groups: filters (i.e. show/hide) and sorts (i.e. reorganisation). | Filters: Asset type -> Image, Dashboard -> Grid, Plugin Management -> Extensions, Tag, Search Sorts: A-Z |
Based on this (and what we have in the UI designs linked above), I think we can quite easily (easily in terms of design more than implementation...) remove the sidebar, and move most items into the location bar (as we'll have a lot more space in there with no sidebar).
If we consider the following:
- Back buttons no longer needed when breadcrumbs is released
- Action buttons are shown to the right of the location bar in the designs (in the case of 'add' actions, these have been included in the main page area -- see 03-dashboard.png for an example)
- View buttons are to the left of action buttons
The only type of button which isn't covered in the UI designs is the 'link' type of button, of which the only uses are:
- Plugin Management -> Get more plugins
- Course editor: Project settings/Configuration settings/Theme picker/Menu picker/Manage extensions
These could be moved into the top nav bar:
- 'Help' moved into the global menu
- 'Log out' button moved into a dropdown shown on user name click/hover, or into the global menu (user profile settings could also be moved here, and the link removed, as it's not really very user-friendly)
- All items in 2. merged into a single 'project settings' page (this would need to be split up into sections to avoid confusion)