Forum Moderators: open
The idea is that you have one file for your menu (or footer, or whatever), and in each page you make a "call" for the server to include that file in the document it serves. So you only code your menu in one spot, but when a page is actually served that mark-up is included. If the end user does a View Source, they see the menu code and not the code for the include.
In the default situation, this means that the file extension for the page is .shtml. However, there are ways on most servers to allow the extension to be .html and still have the page call an included file.
[edited by: tedster at 6:35 pm (utc) on Oct. 16, 2004]
I have devised a system that uses frames if javascript is available and falls back to Iframes if not. The system is too complex to explain here and I have yet to upload it (as part of a site overhaul) so I can't sticky a link to you.
In fact, with { position:fixed } using an Iframe, the nav bar can be permanently visible (non-scrolling) but this is not supported by IE.
Kaled.
This is the main reason why I prefer using an "extended" replace function to edit menus, rather than a bare-bones included file of some kind.
So even though I use a navigation bar system, I also have a link-to-same-page on each index page. Since this link is at the top-left of the page (small and discrete) I find the page transitions appear tidier with this consistency.
Kaled.
Make sure you have a personal web server running on your computer; I found that apache used too much resources so I installed KF webserver from [keyfocus.net...] (but found this product from www.nonags.com). You must also download and install PHP (I chose PHP version 5). Then configured KFWS to use PHP (see FAQ on their site).
It works like a dream!