@miklb: Given that WP has by now achieved quite some notoriety for trouble and lack in the design part, I do believe that design discussions ought to be part of WP. If you still think that not, I have no problem with that ;-)
@ladydelaluna: You're still misunderstanding and misrepresenting what I say. I'm not argueing that one switch back to tables and do away with CSS. While I can understand a CSS-fanatic coming to that conclusion by applying one's own (CSS-only-and-for-everything) stance to that of the other party, it's close to being an insult to someone of my opinion, which is that CSS at best is one solution of many, for one situation and not for others.
And sorry, tabled design is very much a classic. Looking at the VAST majority of CSS-designs out there, and right now I very literally mean EVERYTHING but maybe a minuscule sliver 0.000001%, all I see are CSS sites EMULATING tables. Given that you can do much more and quite different things with CSS, doesn't it astonish anyone, that what it's most used for is recreating a tabled design in divs?! And this not just by the recently "converted" designers, but even by those swearing on the "huge variability" in CSS right from the start?
I've seen so many CSS/XHTML files these past years, which bend over twice and thrice backwards to achieve the MOST likeness to tabled design as possible, often hopping through the most elaborate hoops of coding to do that (in spite of the fact that just this can be achieved with a much, much leaner code in tables themselves). You can't notice that and still think tables and tabular page design isn't a classic.
@manstraw: I made two else identical installations for a client, both on the same server, a WSB one and a WP one, so he could compare and decide which system to use.
I for myself did some comparing on performance and cross-browser/backwards-compatibility because it was a perfect casestudy for me too. Both relatively small CMS, both sites with the content separated from the design, and as the design and setup was practically identical, comparison was easy. I didn't compare sheer performance of the CMS software, instead I only compared and analyzed pageloads and pageweights. And the tables clearly won out there.
I'm not even saying that with a more complicated design than what I usually do this might not have been different. But using a simple, straightforward classic two-column layout, even including one nested header table, the tabled design still won on actual size and loadtime.
The ratio was somewhere along 1 (WSB-tables) : 1,6 (WP-css) and to me at least that speaks a clear language. And the WP installation was not even truly cross-browser-fast, whereas the tabled WSB displayed nearly identically everywhere.
In case you're interested, the client decided on WP in the end, because he liked the admin interface better, I finished the installation for him (with a resulting ratio of 1:1,8 after that) and he's happily using it by now. He is on a fast server, with lots of bandwidth, he can stomach the money he has to pay for that easily, so it doesn't really matter for him whether WP rakes up more of that than WSB. On a slower server or one with less bandwidth allowance I'd have quite clearly told him to go for the other solution.
If you look at the bare files called and their sizes, it's only logical why the tabled design wins out. As I already said, the size of such a simple table code is far smaller than the size of the CSS+html emulating the same table for all browsers and backwards. It's quite funny how you all here tend to negate that little fact.
@vkaryl: I'm a webdesigner, many if not most people I am in contact or friends with are some way or the other net-savvy, tech-oriented and have professional relationships with the net.
I know of no one (literally: not one person) who does more than bid on Ebay, watch violent little video snippets or write an email with these socalled "non-traditional" devices. I have yet to meet someone who actually surfs with his pda or cell phone. It's impossibly expensive, it's slow like hell, it's uncomfortable and you need to carry around a magnifying glass to read.
And what's even more interesting: everyone (literally: every person) who has a pda or other "non-traditional" device also has a computer/a laptop and surfs on those.
Currently, and due to discomfort for a long long time yet, I see no reason to provide content for devices which are not commonly used to view this type of content, unless there is a truly good reason to do so. One of these very good reasons would be the intranet site of a firm handing out pdas to their employees for quick referencing. I can think of very few other equally good reasons.
Seriously, who would look at a site with hours-long reading content on a device where 10 minutes cost him three bucks (while at home he pays at most 1cent for the same time and can read much more and much more comfortably)?!
Until we've reached that sci-fi age where glasses project the whole screen onto your retina and this service costs as little as dialup internet does, there is to me little sense in trying to cater to this for the vast majority of sites. And if we sometime reach that point of technology, we don't need to adjust, as the projection will be as good as sitting in front of a fullsized screen.
I wonder what you think are the benefits for a normal content-driven site and even the majority of commercial sites to be accessible via pda or cell phone? Does anyone here truly believe, that any major shopping is done that way? Does anyone truly believe people have so much leisure time and are so rich to sit around and surf (expensively) instead of doing what one usually does when leaving the house? What is that projected target audience for this? How much income will it generate for a site?