UI : refactor aegir navigation
adrian - October 20, 2009 - 23:10
| Project: | Hosting |
| Version: | 6.x-0.4-alpha2 |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Jump to:
Description
We need to get rid of the menu block with the 'create content' and all those links that don't make sense in the context of aegir
My idea is to start using a primary menu, with a menu item for each of our primary entities (sites, platforms, servers, tasks), with the 'add X' button on said page.
i've made a simple little wireframe.
we should also look at where we can move the other entries in the menu (log out, etc), so that we can get away with hiding the menu block (which is just taking up space)
| Attachment | Size |
|---|---|
| workflow.png | 48.27 KB |
#1
Maybe all hosting related menu items (add site, platform, client etc.) can be moved to existing top menu item "Hosting"?
Log-out is available directly in the admin_menu.
#2
i thought about that , but admin_menu is only visible to admins, and is not really an end user thing.
#3
But we are using admin_menu, anyway?
Even if not used, all items like add site, platform, client etc. could be moved under "Hosting" top menu, doesn't mater if displayed by admin_menu or other custom panel/menu.
Menu stuff for logged in and not logged in users can be hidden/displayed using menu_per_role (for example), and it will work also without admin_menu, so we can move away standard login menu block.
Another story is default welcome page with log-in link, but without log-in standard block.
#4
mucking around with admin/build/menu
http://skitch.com/vertice/nryd8/hosted-sites-t
#5
we'll take a look at this after alpha 4 , where we've refactored our node types