Well, Rob, the good point is that it works. But in the words of the Old Master, "there is much yet to learn, young Grasshopper."
The most egregious error is that you are not using any header tags (<h1>Main Heading</h1>, <h2>Top-Level Subheading</h2>, <h3>Second-Level Subheading</h3>, et cetera) except on the individual menu pages. Because your site is using graphics rather than text for the main page heading, it might not be apparent why this should be important. It's not just about the size and alignment of the text; it's about the structure of the document. A machine can't read your page and make sense of it. Not only does that mean that visually impaired users can't access your page (they rely on screen readers, and often on browsers that display all text at a single size and don't display images at all), it also means that search engines can't tell up from down.
That brings me to point number two -- your images are
just images; there is no alternate text. The alt="some text goes here" attribute on an image tag should not be thought of as optional if the image is anything more than a decoration. (And if the image
is just decoration, then it should come from your CSS style sheet, not from your HTML markup.) If your "Dignan's Catering" logo image fails to load for whatever reason, there is nothing but a hole in the page left behind because you have
alt="" in your markup. The text in the
alt attribute is what the browser will display if the image cannot or will not load. The same thing applies to your menu images -- there are no navigational clues left if the images don't load.
Speaking of the menu, there's a spelling mistake in the word "Menu's". I'm not mentioning that because I want to make fun of you, but because the mistake is in an image, not in some text. You may be able to correct that easily right now, but let's imagine that it's not a spelling mistake, but rather a menu item that needs to be changed later on. It's going to be very difficult for anybody who doesn't have exactly the same version of that font and exactly the same image editor to match the rest of the menu (different versions of the font may have slight differences, even if the name and "feel" are the same, and different image editors handle text in slightly different ways). Whenever possible, try to use text instead of images. If you need to use a particular font to get the effect you want, then you can use the
@font-face CSS rule -- that lets the user's browser temporarily download and use a font that they may not have installed on their machine.
Oh, and you don't need to use anything like the mm_menu script for anything anymore. CSS will do the same thing better-faster-cheaper through the use of the
:link,
:visited,
:hover and
:active pseudo-elements. You might want to Google for "CSS menu" for some examples.
I hope this doesn't come off as discouraging. There is a lot of old and outdated information in libraries and on the internet that can lock your web efforts into a 1996 time bubble, but there is also a lot of really good, up-to-date, "best practices" stuff out there as well. Nobody's expecting you to become an instant expert; learning takes time. But it helps to know why you're doing what you're doing, otherwise you can become a cargo cult developer/designer, just doing things the way we had to do them in the bad old days without understanding that there are much better ways to do things now.