I've playing around with CSS for a few weeks now, and have started to convert the relio design to table-less design

Here is the new one http://new.relio.com

But now I am in a snag, the "plans details" page .. with dozens of tables

http://www.relio.com/linux.html

any ideas whats the best way to convert those to CSS Table-less .. do I have to create a "div" with floaters for EACH line ? (just the content area)

comments suggestions much appreciate

Carlos

Tables are not used for layout, but they should be used when you need to display tabular data. What i suggest is that you style the table using css and not replace it with divisions..

Tables are not used for layout, but they should be used when you need to display tabular data. What i suggest is that you style the table using css and not replace it with divisions..

So keep the tables, and style them with CSS ?

Maybe I was going too far with the "no tables" policy :)

Exactly....
Div;s are not always a replacement for tables. :)

You could check these links for xhtml table style
http://www.topxml.com/xhtml/articles/xhtml_tables/
http://dtd.nlm.nih.gov/publishing/tag-library/n-5s40.html

flak is right some times tables are good. I know a few sites and designers want to completely eliminate tables but tables do have a purpose.

Just to back up what the previous posters have already said there is no need to get rid of the tables in this instance. Tables themselves are perfectly fine and valid X/HTML and should be used where necassary, which is the case here. When people talk about table-less design they are not, generally, talking about removing tables entirely from their projects but just removing them as a framework for your page layout.

Tables are neither inherently good or bad. Like any other element, they have their uses and they can either be used properly or improperly.

If you're using them as the framework for your layouts, you're using them improperly. If you're using them to display data that much be expressed in tabular format in order for it to be interpreted properly (like spreadsheet data), and if you're using table headers, summaries, etc. properly, then you're using tables properly, and you should not look for a substitute for this.

Using tables for layout creates such a mess, as with your nested tables problem, that it becomes very difficult to directly convert them to 'table-less'. This is a perfect example of why you should never use tables for layout.

The best thing to do is ignore the code of the previous version and just start from scratch.