Posted by adrian on October 20, 2009 at 11:10pm
| Project: | Hostmaster (Aegir) |
| Version: | 7.x-2.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Issue Summary
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 |
Comments
#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
#6
Subscribing.
#7
partially implemented in the dev-server_nodetype feature branch which is about to get folded in.
I have added primary links tabs for sites / servers , and we'll be adding clients / platforms too.
#8
I added the tabs for clients and platforms last night , but now i'm starting to think about the create node links.
I think perhaps the best way to do that is through secondary links.
#9
I'd imagined something like the shot in #7 would be the way to go, looks ok.
I'd also like to see us drop admin_menu.module. It annoys me greatly the way it randomly drops down when hovering over the header area, that's only going to get worse with the main menu up there.
That leaves a problem of what to do with admin links... admin.module is more compact but probably wouldn't sit well with aegir.
Have a column added only once we've clicked on an admin link?
Maybe keep admin_menu and only have it appear on /admin pages.
#10
the primary nav links are not going to contain items like admin.
the IA is that the tabs are listings of the entities, and beneath that there is the add new [entity] link.
#11
subscribing
#12
see http://drupal.org/files/issues/workflow_1.png again.
im puzzling over how to implement the single create [entity] link. I'm thinking secondary links with special styling is the way to go.
as far as admin module goes, i think it could work.
#13
Can't we just build our own menu? We could declare one and let the theme throw a block anywhere we want... I'm not too familiar with menu hacks though, so I may be completely out of whack here.
#14
that wouldn't be backwards compatible with any theme
they would need to modify their theme to use aegir , so we are sticking with what drupal provides.
#15
In D7 we have menu_local_actions, so this would be super easy.