Best why to do drop down menus

  • Thread starter Thread starter JoeM
  • Start date Start date
J

JoeM

I have a webpage that has about 118 pages. There are menus needed on about
90 of these pages.
 
Looks good, but I may need a little more, 90 of the pages need to have the
same menus, I don't want to change the code in all of the pages, and not
all html files are located in the same locaton (but they are all are on the
same domain,server).
 
That's not a problem. Use a server-side or FP include for the menu. But
what do you mean by not at the same location? Do you mean that you are
linking cross-domain? That wouldn't be a problem either.
 
Put the menus in a dynamic web template file (FP2003 only) or Server Side
Include (SSI which requires all files with the included page to have an
*.shtml extension) or Frontpage include component page (FP 2003 & earlier).

You will then have the one file with the menus but you still would have to
go through 90 files and include the file or attach the template to each
one - a lot of work nonetheless.
 
All pages are in the same domain, example I have menus top
title,(FieldDeployment, OrderingShipping), like (File, Edit) are all folder
names, and inside these folders are the HTML documents that are linked to
the submenus of this menus.
A little confusing, and alot of work.
 
Well about 90 files I need to change when I add or change a menu. If I
could have one place I can change this it would be great. I will try the
namic web template file since I am running Frontpage 2003. Thanks
 
That's a perfect justification for using an include. One file. One set of
changes. One page to publish. All pages reflect the changes.
 
FYI: FP will not manage the links, so the link would have to be absolute URLs to the pages.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
I spent a long time learning how to use layers and behaviors to do drop down
and flyout menus. Then I found AllWebMenus. Best $60 you can spend. I can do
menus quicker and with better control now.

http://www.likno.com/allwebmenusinfo.html

I put the AllWebMenu into my .dwt and it spawns across all my linked pages.
 
Using Jim Buyen's tutorial there will be no problems with links or
JavaScript. I use a variation of this on www.rxs-enterprises.org,
where the FP behaviours have been moved to an external .js.

There will be problems if any links are generated using JavaScript -
but no problems using behaviours to manipulate the layers.

You could use a Dynamic Web Template instead of include files, which
may make things even easier.
 
I would never replace an HTML menu with a javascript menu system. It's a
huge step backwards in usability, accessibility, and good practice. But -
whatever floats your boat, I guess....
 
Looked at you site look good, I am in the middle of trying the Dynamic Web
Template, and I will see how it turns out.
 
Back
Top