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)
| Comment | File | Size | Author |
|---|---|---|---|
| #19 | Aegir-add-X-links.png | 60.69 KB | steven jones |
| #7 | Screen shot 2010-02-11 at 8.20.54 PM.png | 16.58 KB | adrian |
| workflow.png | 48.27 KB | adrian |
Comments
Comment #1
omega8cc commentedMaybe 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.
Comment #2
adrian commentedi thought about that , but admin_menu is only visible to admins, and is not really an end user thing.
Comment #3
omega8cc commentedBut 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.
Comment #4
adrian commentedmucking around with admin/build/menu
http://skitch.com/vertice/nryd8/hosted-sites-t
Comment #5
adrian commentedwe'll take a look at this after alpha 4 , where we've refactored our node types
Comment #6
q0rban commentedSubscribing.
Comment #7
adrian commentedpartially 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.
Comment #8
adrian commentedI 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.
Comment #9
adrinux commentedI'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.
Comment #10
adrian commentedthe 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.
Comment #11
wik commentedsubscribing
Comment #12
adrian commentedsee 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.
Comment #13
anarcat commentedCan'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.
Comment #14
adrian commentedthat 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.
Comment #15
steven jones commentedIn D7 we have menu_local_actions, so this would be super easy.
Comment #16
steven jones commentedThis will need to wait until we have pages to put the links on!
Comment #17
Anonymous (not verified) commentedCan we merge this with #1417920: Add an "add site", "add platform", "add server" button to listing pages somehow? Seems to me it's really discussing the same issue?
(I *hate* issue queue cruft :))
Comment #18
steven jones commentedIf this doesn't get into 6.x-2.x I'm going to cry.
Comment #19
steven jones commentedI've simply added extra local tasks for the add links on the listing pages which I think look reasonable until we can change them to local actions in D7. This is what the platforms one looks like:
Comment #20
steven jones commentedSorry that code was in 6.x-2.x.