Forum Moderators: open
-CSS Nav
-Javascript Nav
-Custom Firework Created Nav
I mostly use CSS but when I need something a little more creative I use Fireworks to create one. But is using fireworks bad because of all the extra code (tables, img loading, ect...) that is included? Plus it sucks to update but I can be a little more creative.
Thanks!
This is because not all browsers support JS, and some companies force their users to turn it off (and some people just turn it off anyway).
Unless the page is a special page, I NEVER rely on JS as a critical aspect of my navigation. One of my tests is to turn off cookies an JS, and poke around the site.
I always roll my own, so I can't comment on Fireworks (I have it, but never use it -I always use Photoshop to prep my images).
I'm not a big fan of flyout menus.
BTW: You may want to disable the link before the forum mods get to it. We're not supposed to post external links [webmasterworld.com](except for some well-known ones).
Welcome to WebmasterWorld! Don't let the posting rules get to you. This is a great forum.
[edited by: cmarshall at 8:18 pm (utc) on Mar. 26, 2008]
SitePoint is a well-known source:
SitePoint's Tutorial [sitepoint.com]
The famed "Son of Suckerfish" menus (Can't find a single, good link, but try Googling it) are JS-based.
[edited by: encyclo at 5:16 pm (utc) on April 22, 2008]
But way back when I was learning how to write CSS Menus, I learnt from a website called Max Design [css.maxdesign.com.au] which had tutorials on the simple things, which slowly became more complicated with each sub-tutorial.
Other than that, I would just write a CSS navigation menu and have the CSS Forum lads tear it apart. I'm sure cmarshall & I would be happy to do so :)
[edited by: encyclo at 4:45 pm (utc) on April 22, 2008]
<edit> Added note. </edit>
Missed the Stu Nicholl's reference. Yes, awesome. Cutting edge and not for the beginner, but setting a standard for what can and will be. And most of it works just fine even in IE right now.
Literary Moose (CSS Destroy), now logotenmoose is way out on the edge, but absolutely sound development. Want to be top gun in a few years (or even today) study at this site now. I have a site that does not even allow IE users; a private site for a small circle of friends. We all have a site that only allows Firefox or Opera users only, and what I learned from CSS Destroy goes there. (Since it doesn't work anywhere else:)) Banning IE users is as much fun as the CSS.
[edited by: encyclo at 4:48 pm (utc) on April 22, 2008]
as for menu tutorials - this search [google.com] reveals two of your very own moderators tutorials, for SE Friendly CSS menus - at the top of the SERPS ;)
[edited by: encyclo at 4:48 pm (utc) on April 22, 2008]
The famed "Son of Suckerfish" menus (Can't find a single, good link, but try Googling it) are JS-based.
One was on a vertical menu that had sticky popups / flyouts (known 'bug'), the other was on a horizontal menu with centred links. The flyout menus were off in IE (but that was fixed with a IE-only CSS comment.