(If a moderator reads this and can be bothered, could they please re-name this thread "Will I use CSS tables or Joomla?" or whatever makes more sense to career web designers & coders? You'll see what I mean.)
It's by Kevin Yank at Sitepoint.
My main issue is I'm learning CSS so that I can change the "look" of Joomla. If I'm using Joomla anyway, do I (at this early stage of my CSS career) really have to learn how CSS replaces "Tables" espcially when this process seems so controversial and difficult, and Joomla should be able to do it for me? (I promise I'll be good and get into CSS tables later... and one day want to hand code a whole site from alpha to omega in something as basic as Smultron).
Why do I say CSS "tables" are controversial and difficult?
Because the Sitepoint podcast (on iTunes) recently advertised their book (above) and interviewed one of the authors, Kevin Yank, and it's all about how most people do CSS "tables" the hard way. I think I've used up my training budget subscribing to Lynda.com. Any guesses as to what he'll cover in the book? Anyway, if CSS tables (or their replacement) are such a controversial area right now, can I just forget learning about CSS tables for the moment and concentrate on layout in Joomla? How much extra code does Joomla add? Doesn't it take care of tables and navigation bars and all that for me, and do basic page layout? I'll probably be able to "tart it up" in the CSS just fine, but can I just let Joomla look after the page elements layout?
(Another thought... does Joomla layout in XHTML and then add php scripting stuff on top?)
BTW, the Sitepoint podcast seems to be a great round up of web industry news, browser standards rants, what's happening with various software, etc. I recommend it — it's only 3 episodes young and I recommend downloading them all from iTunes and checking it out. I've been "out of the scene" for a while and need all the help I can get, especially as my wife is strictly print and it's just her and I in this family studio.
It's by Kevin Yank at Sitepoint.

My main issue is I'm learning CSS so that I can change the "look" of Joomla. If I'm using Joomla anyway, do I (at this early stage of my CSS career) really have to learn how CSS replaces "Tables" espcially when this process seems so controversial and difficult, and Joomla should be able to do it for me? (I promise I'll be good and get into CSS tables later... and one day want to hand code a whole site from alpha to omega in something as basic as Smultron).
Why do I say CSS "tables" are controversial and difficult?
Because the Sitepoint podcast (on iTunes) recently advertised their book (above) and interviewed one of the authors, Kevin Yank, and it's all about how most people do CSS "tables" the hard way. I think I've used up my training budget subscribing to Lynda.com. Any guesses as to what he'll cover in the book? Anyway, if CSS tables (or their replacement) are such a controversial area right now, can I just forget learning about CSS tables for the moment and concentrate on layout in Joomla? How much extra code does Joomla add? Doesn't it take care of tables and navigation bars and all that for me, and do basic page layout? I'll probably be able to "tart it up" in the CSS just fine, but can I just let Joomla look after the page elements layout?
(Another thought... does Joomla layout in XHTML and then add php scripting stuff on top?)
BTW, the Sitepoint podcast seems to be a great round up of web industry news, browser standards rants, what's happening with various software, etc. I recommend it — it's only 3 episodes young and I recommend downloading them all from iTunes and checking it out. I've been "out of the scene" for a while and need all the help I can get, especially as my wife is strictly print and it's just her and I in this family studio.