questions about column and row div layouts

I've been having some trouble creating CSS-based layouts that include 3 columns, a header, and a footer. For example, in what should be a fairly simple layout (here):
http://www.etvlog.com/log/inProgress...herlayout.html

... I can't figure out why the top of the "right hand column" doesn't line up by default with the other two columns. I've even given it additional width, in case the borders or margins were adding pixels, but that doesn't seem to be the issue.

In order to address an issue where footers don't clear multiple body columns properly, I've added a hack from this page:
http://www.shauninman.com/plete/2006...nline-absolute

... but I wonder whether a simpler and more elegant solution exists. I'd also love to know why this actually happens.

A few other questions, such as: how would I add some "cell" objects to the middle column, without skewing the rest of the layout? For instance, if I wanted the middle column to contain something like a two-row table, with two cells in the top row and one cell in the bottom row?

Similarly, how would one adding two "rows" to the header, and having one column spanning both rows on one side?

Perhaps the answer is to think of each of these "cells" as a separate div? But it seems that things could get even uglier that way.

Thanks for sharing your thoughts.

Thanks... but that site/layout does not include a footer, nor any cell layouts within a column or row. It is a nice layout, and I actually used that as one of my starting points for this project, but things stopped working very quickly once I tried to insert a footer, add row and column "cells", and manipulate values. Unfortunately, it doesn't help with what I'm trying to do in this layout.

I'd appreciate your additional thoughts though.

Thank you.

Are you looking at the site's layout or the tutorial on the site?

First, my mistake: at first, I thought you had linked a different site. Not sure why; must have been an "operator error". My apologies.

Turns out that "clear:both;" from that tutorial is likely just what I am looking for. That's an informative, well-written piece. Thank you.

Any additional advice on dividing a individual div into "cells" to similate a table layout, without affecting the layout of the entire document? I assume there's some "float" and "clear" technique involved, but when I've tried this, I couldn't reproduce the effect I wanted without affecting other floats outside that particular div and destroying the overall page layout.

I'm not sure what you're trying to do. A div is a cell of sorts, but each div is independent. There is no way to get a div to respond to the dimensions of another.

When you migrate to CSS from tables, you need to overcome the mentality that websites should be divided into cells.

Oh, and if you're using CSS to display raw data, it should be in a table. I've seen some people so thoroughly disgusted with tables that they used groups of unordered lists to simulate a table. Tables aren't evil, they just don't have a place in website layouts.

I'm probably going on a stray tangent with this post...

That is indeed what I'm trying to do: organize content into "cells" without using labels. I think I need to shift gears and visualize the layout in another way.

Yes, I do. I most easily visualize a layout as a collection of rows and columns. Again, I need to rethink this approach.

No, not really. "table" is a valid HTML element and has a valid purpose. But then there could be a discussion on the definition of "raw data", and why some people include a series of links (i.e., a navbar) among this category.

By the way, I'm not sure why, but the "instant email notification" feature of this forum seems to work sporadically at best: I was notified of only one of your replies, even though I read the reply immediately afterward. In any case, I'm very glad for the help.

But links are lists, not raw data. Data as in a table like this (compliments of the W3C):

Attached Images

mergedcells.gif (2.5 KB, 38 views)

Links are most often lists (as in navigational lists/navbars), but they can be returned as raw "data" in part of a data set.

BTW, by "No, not really", I meant that I didn't think your post was headed on a stray tangent. Your response was related, and I appreciate your perspective.

Thanks.

Okay. Don't forget lists are way easier to read and use less code though! They're also best for accessibility where navigation is concened.