|How Would You Create Nav Bar In Dream Weaver|
Question For Dream Weaver Experts
I just took my Go Live 150 page website, and stripped out the Go Live code that made the Navigation Bar, Footer, and Right Column on most of the pages.
I have now opened it up as a site in Dream Weaver.
What tool would you use in Dream Weaver to create the Navigation Bar and Footer so that it could be easily up-datable in the future?
Standard server-side includes, or php includes.
You can make the navigation a "library" element and paste it in to each page. Whenever you update the master copy (which you'll find in your Assets window), all pages will get updated.
Or you can make a template page or pages for your site and place one or more different navigations in there, and whenever you change the template, that will update all files that depend on it.
Sonjay's answer, though succinct, isn't actually using Dreamweaver, which was the question you asked.... <smile>
[edited by: DerekH at 12:25 pm (utc) on Sep. 24, 2006]
Well, you can indeed use SSIs or php includes "using Dreamweaver." And they are indeed the tool I use "in Dreamweaver" to create things like navbars and footers so that they are easily updateable. Note that the OP didn't ask "what proprietary Dreamweaver feature would you use?" He asked, simply, "What tool in Dreamweaver would you use?"
Purposeinc, to clarify: If you create a DW template, and base all your pages on the template, or if you use DW library files, you can update the template or the library file, and DW will automatically propagate the change to all the pages in the site that are based on that template or use that library file. You must then upload all of the changed files to the server for the change to take effect.
If you use some form of standard includes, you edit that one file and upload it to the server, and bang, you're done.
Both ways will work. I prefer includes.
Yes, there is always a trade-off. Nothing is black and white in this world :-)
It's not quite as one-sided as it sounds...
I have used SSIs in the past, but I believe that most search engines regard an SHTML file as "liable to change" even if the date modified on the file is constant (because the SSI can change the "composite file" even if the container file is unchanged.
This can mean that you serve a lot more pages to search engines than a static site that returns a 304 (page not changed) in response to a page whose date modified is older than Google's cache.
One of my ISPs charges bandwidth on a pay as you go basis, not a monthly allowance, and reducing the search engine bandwidth without reducing the bots' willingness to visit is something I prefer :-)
Thank you both for your comments on this so far. Due to my beginner status on making web pages, the library and template options sound the easiest for me to do.
Of those two, what are the advantages or disadvantages of making my Navigation Bar, Footer, and right column out of a Template, vs. Three Library items?
Also when I am making a template, which I am experimenting with at the moment, which of this text can be left out, and which should be left in the template?
|<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
<meta http-equiv="content-type" content="text/html;charset=utf-8" />
<meta name="generator" content="Keyword1 Keyword2 Keyword3" />
<link href="css/basic.css" rel="stylesheet" type="text/css" media="all" />
<style type="text/css" media="screen"><!----></style>
First, it actually is quite one-sided. I use includes in every site I create, and there's nary a .php page or .shtml page in my entire portfolio. It's a simple one-line entry in your .htaccess file to parse .html pages for php or ssi. The search engines don't know and don't care.
With that said, I would ask, Purposeinc, how many pages your proposed site will contain? For a site of just a few pages, you would do fine with templates or library items, but if your site will have dozens, or hundreds, of page, you should just bite the bullet and start with includes from the get-go. When you find yourself uploading 88 (or 188) files for the umpteenth time just because you made yet another small change in the navigation, you'll wish you had used includes. Oh, I just noticed in your first post you said 150 pages. In that case, I really, strongly, have to recommend includes over templates or library items. It's really not hard, even for a beginner.
In php, it's like this:
<?php include 'navigation.html';?>
With SSIs, it's like this:
<!--#include file="navigation.html" -->
Your navigation.html file would contain your navbar code. Just your navbar code -- no head tags, no body tags, nothing but your navbar code.
It's really quite simple. But you can do it however you want.
If you still want to use templates or library items, given that you already have existing pages, you're probably better off with library items than a template. Usually I would recommend a template over library items, but for a new DW user, trying to apply a template to existing pages will be nothing but an exercise in frustration.