By debonator on

I've checked out most available options for drop down menus (nice-menus, the roople theme, etc) and it's start to look like hard coding the menu (in the form of nested lists) might be the easiest thing to do. I'm thinking i can just put the list in the page.tpl.php file and call the necessary javascript. I'm basically thinking about of following the Son of Suckerfish directions here: http://www.htmldog.com/articles/suckerfish/dropdowns/.

is there any good reason to *not* do this? i understand it might not be the most elegant solution, but i can't see any reason to not use it.

am i missing something here? is there a good reason to get all fancy?

thanks!
debra

⋅ Categories: Drupal 6.x

Comments

Jeff Burnz’s picture

Jeff Burnz commented

The answer is, as always, it just depends. The main thing you loose is the ability to update the menu items via Drupal menu system and other things such as being able to move the menu block if you want to later on using Drupal block settings.

I think its fine, but I would probably use a block (add a block and place your html there) rather than hard coding them into page.tpl.php, just to keep my page template clean and at least offer some ability to edit the menu directly via the blocks UI.

Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
debonator’s picture

debonator commented

ok, i'll give that a whirl. it does sound easier to maintain that way. thanks for the advice, jeff!

clau_bolson’s picture

clau_bolson commented

Just a quick question: if you put menu's code in a block, still you have to embed the javascript required to work in IE in page.tpl.php, don't you?