You'd do well to forget about css layouts for the moment, and
concentrate on making your pages work in a wider range of viewport
widths, using html to properly structure your pages by using headers,
lists, paragraphs etc., and lastly getting rid of other presentational
html such as font tags.
Thanks for the help although that last paragraph blinded me with science eg
"wider range of viewport widths". I take it that might mean I should make
it look better in a higher screen resolution as I have only designed it for
800x600?
I am trying very hard to produce a site which in markup compares to a
correctly punctuated sentence. (While of course maintaining my Bellringers
section, where it all started.)
When I used Frontpage I was criticised for 'bloat' and incorrect HTML. I
dumped FP which, incidentally, was by far the simplest way to build a
website.
I rebuilt all my 'million' pages so that each was validated.
I made mistakes along the way, but felt I had got there even learning some
HTML and css (which I had never heard of when I began).
The criticism now arose that 'frames are for data' and that I should not
use them to hold images and buttons in place. Since my site consists
largely of images and buttons, I have to be sure that any advice I follow
is 'better' and not just some pedant's view of heaven.
I had a look at creating the css equivalent of a 2x2 or 3x3 table to fix
the positions of my images in the manner I desire, and although it all
worked well in Firefox, IE beggered it up if a picture was a tad too big.
However then someone kindly chipped in and advised that I should stick with
tables as 'scaffolding' (my term), but set up the basic table in css.
My question here was really "what difference does it make whether the table
is in a stylesheet or purely in the HTML body? It's still a table."
I have all the time in the world to change yet again, but need to be sure
of the course to take.