Remember to add "http" in front of your URL -- that aside, I still see the work in progress as reporting a "The requested URL /index1.html was not found on this server."

Lynnkeen, just a couple thoughts I suppose. First when it comes to CSS, try to name your IDs and classes after something that makes sense, like "topBox", "banner","pic" vs just numbering them. Of course you are free to do as you please, but I have found it is just easier to come up with a naming convention that works for you that makes sense, hopefully to others as well to a certain extent.

As far as the iframe element, there is no way (without using ajax) to load a certain portion of the content dynamically while keeping the rest of the page static, which is what you are accomplishing with the iframe. If you like that functionality, just keep the iframe. As far as CSS goes the iframe is not a problem. It is a problem with search engines and usability though and typically you would just create a sepearte page for each section. One of the cool things with CSS is that you could load those images through and external stylesheet, and then those images (and the stylesheet in general) has been cached the viewers browser, so new pages will load much faster.

Basically you need to figure out what functionality you want there. You can keep the iframe, or create a new page for each section. If you plan on having enough content in that section where you would need a scroll just set a div in place of the iframe, and set overflow to scroll, and it will act as a scrolling window for the content.

I hope that helps

lynnkeen,

instead of using iframes you should think about using a "header" and "footer". Would possibly save you the problems that iframes create, and could possibly speed up your website. Here's a tutorial on how to do this.

http://www.choicetemplates.com/tutorials.php?name=headfoot

cheers
-Phil