Hey guys,
I'm knee-deep in Aurora and I'm loving it. One of the things that has been eating up an inordinate amount of my time is integrating Superfish with Aurora gracefully. Using the SF module, I can get along pretty quickly, but it introduces nasty limitations with regards to breakpoints (namely, I get one! Where's the love?!), as well as a bunch of other stuff I won't detail just yet.
On a side project, I grabbed Bootstrap and started playing with it, without even messing with LESS. I have to say, for a quick, out-of-the-box solution, just the fact that it has the Superfish-like menu bar figure out from the get-go is a huuuuuge deal (though I know in the longrun, I much prefer working with Aurora as a system). Any possibility of making some really basic Superfish-ish thing that integrates with Aurora, such that you can easily set breakpoints etc? I think that's something that would really get people into this theme (menu handling is a pretty important aspect of mobile design, no?)
Thanks!
Charles
Comments
Comment #1
Snugug commentedI'm going to assume you are unfamiliar with the work the maintainers do outside of Drupal and therefore this was suggested sincerely as opposed to being a troll. As such, let me familiarize you with our work:
Both Ian and myself are strong opponents to Twitter Bootstrap and the general idea of drop-in "responsive" solutions, preferring instead tools to allow you to create your own styling and design as needed. In fact, Aurora was initially built and is designed specifically to not provide the kind of things that Bootstrap or a similar CSS System would provide and instead actively encourage you to create your own because that's what's needed to create truly successful designs, responsive or otherwise.
All of this being said, while I'm not sure the exact issue you're having in regards to Superfish and breakpoints, I'm willing to be it's because Superfish is a solution not meant to be responsive that requires a significant amount of overrides in order to get to be responsive. I would not encourage its usage, or for that matter usage of pretty much any out of the box solution. Instead, I encourage you to learn how to create one using the raw tools of CSS (Sass in Aurora's case) and JavaScript; a basic responsive menu takes very little of both.
Comment #2
Snugug commentedComment #3
mausolos commentedWell, yes, I'm very familiar with your guys' work, and no, I'm not trolling. I get what you're saying, but hear me out:
One of the big reasons I (and obviously many other) developers prefer open-source solutions - and Drupal in particular - is because of all the wonderful code that's out there that one can use to accelerate a project. Could I come up with a better framework solution than Drupal for my projects, or a better website development language than PHP? Sure, I suppose I could, but why? Instead, I opt to download Drupal, download a bunch of modules, switch them on and go. Does that get me all the way there? No, of course not.
Mobile-friendly drop-down solutions have been thought of. Smarter people than I, and those more handy at CSS and JS have come up with working solutions. Myself, I'm more heavy on the PHP and data side of things. Why should I have to reinvent the wheel all over again? I'm really into your guys' crusade. You've sold me on it. I'm not suggesting a full-fledged solution, but some basic (umm, less basic than SASS, CSS or JS), oft-implemented tools would be nice.
Comment #4
mausolos commentedThis is a rough recipe, but here's more or less what I did to make a Superfish-ish menu system. I hope someone finds this useful:
First of all, I referenced http://responsivenavigation.net/examples/multi-toggle/index.html. I'm not going to bother including the SASS/CSS that I used, because the example they provide is much more generic and my CSS is very project specific. You should be able to take what I have here and adapt the CSS that the Response Navigation site provides in its example without too much trouble.
Next, I used Menu Block module to create, well, a menu block for my menu. I selected Advanced options tab (in the block configuration page for my new menu block), set "Starting level" to "1st level (primary)", set "Maximum depth" to "Unlimited", and checked "Expand all children of this tree." For "SEMANTIC SETTINGS", I set the Wrapper to "". This was my first menu block, so it was given the ID "block-menu-block-1".
In the template.php for my sub-theme, I added the following:
Then, I created a custom template, "block--nav--1.tpl.php", which I also put in my sub-theme root folder. It contains:
Finally, here's the JavaScript I used:
Comment #5
infiniteluke commentedIt seems to me that project requirements should dictate the kind of menu you build. This project seems focused on shipping ingredients and tools not recipes.