Grouped menu items should have a drop-down for quick access to each subitem without going to a separate page. The drop-down needs a max number, though, since some projects may have dozens or even hundreds of instances a tool. Maybe it could limit to 10 and have a ...more... link at the bottom going to the listing page.
_nav.json
should include the drop down data also.
Diff:
Here's a simple mockup of what the menu could look like. It doesn't have to match this exactly. Just something simple and easy.
This is only for the main 'allura' theme. The 'sftheme' theme doesn't need to be changed yet.
Created #296: [#5599] Create drop-down for grouped menu items (2cp)
Related
Tickets:
#5599The HTML structure used for drop-downs needs to match the HTML we use on other non-Allura pages. We don't have that defined exactly yet. So some of this work can be done, but actually displaying the drop-down is blocked.
I've put corresponding ticket from our backlog (#296) on hold for now. Let me know, when it becomes clear.
Below is a small sample of HTML structure. It uses list tags which are more typical for menus, especially when nested. (It also aligns with menu structure we use elsewhere on SF, which will be helpful for us). It is different than the current Allura menu HTML, so some adjustments will have to be made to the base menu styling, in addition to adding drop-down support. For example: selectors need to be updated for lists. And
class="selected"
used instead of<span class="diamond"></span>
so maybe make thatfont-weight:bold
. Lastly,#top_nav
has a lot of background and border styling that we'll be be removing in SFTheme, so it might back sense to remove it on the Allura theme too. I am not too particular.Make these changes in Allura. We'll do the SFTheme theme separately.
Use
db/5913
as a starting branch. It has the top-level HTML structure already.Closed #296.
je/42cc_5599
.