Tuesday, April 14, 2009

Tables are Inconsequential

I am having a hell of time trying to make a new website for my movie, The Lionshare. I want it to be simple. The way I taught myself how to design a layout for a website, all those years ago, was through HTML tables. This is verboten. Tables were not meant for layouts. In fact, tables killed the web.

I understand what they're saying, mostly. CSS is far more efficient for web layouts, in terms of amount of code (though I don't see why that argument holds so much weight in the age of broadband internet). CSS is meant for layout, and the possibilities are great. Tables are meant to display tabulated data, and website layouts using tables are, in actuality, using a very roundabout way to do what it's trying to do and are very limited in doing so.

My problem is this is not how I learned to regard tables. I learned to layout my websites with tables. In fact, I found it quite freeing, back in 1999 through 2003. I get the concept of CSS, but I'm having difficulty retraining my mind to think of design in terms of CSS.

I want a really simple website for right now. I really do. The problem is I feel pressure from the net elite to make my website the 'right' way. But in trying to CSS it I get bogged down and frustrated. I want to concentrate on content.

Maybe I should just take the advice I heard last night: an inconsequential difference is no difference at all. For my purposes, tables vs. CSS is inconsequential.

No comments:

Post a Comment