Is there any point in learning to use CSS in websites? Or would I be just as well off making a table based site? I am using dreamweaver but haven't made a site in years, everything has changed so much. I see some of the advantages to CSS but writing the code and getting everything to work is just plain annoying.
I don't think there is any point in trying to use tables to make a website. Check out http://www.csszengarden.com/ for a taste of what css can do for you (and those visiting your website).
USE CSS! Dont get yourself into the nightmare that is tables. CSS is much cleaner and you can use one template to define your whole site making it much easier to edit.
I have since discovered a tool for drawing the CSS layouts how you want on a html page. I then copied it over to a external CSS file and cleaned the code up. It may be cheating but I am still learning so it all helps. Thanks for the replies, I know deep down inside that tables are wrong.
I would call it the nightmare of CSS, not tables. Why? Because tables show up exactly the same in every web browser. While CSS loads faster, takes up less bandwidth, is more flexible, etc, tables are 100% browser compliant. There is nothing worse than coding a website in CSS and then finding out it’s all screwed up in Firefox, or Opera, or another browser. With that being said CSS is the way to go if you are doing a lot of websites. If you are just doing your own and don’t want to spend hours (maybe even days) trying to find the CSS hack(s) so your navigation/some element on the page is in the right place, use tables for the layout. Then use CSS for the colors etc.
Sometimes you just want what works, and tables just work.
nylad wrote:
I would call it the nightmare of CSS, not tables. Why? Because tables show up exactly the same in every web browser. While CSS loads faster, takes up less bandwidth, is more flexible, etc, tables are 100% browser compliant. There is nothing worse than coding a website in CSS and then finding out it’s all screwed up in Firefox, or Opera, or another browser. With that being said CSS is the way to go if you are doing a lot of websites. If you are just doing your own and don’t want to spend hours (maybe even days) trying to find the CSS hack(s) so your navigation/some element on the page is in the right place, use tables for the layout. Then use CSS for the colors etc.
Sometimes you just want what works, and tables just work....Show more →
For working, how about accessibility? Or the work required to write the code and then maintain it?
The point of html is different from typesetting. The point of html is to tell the display system what your intentions are and let it handle the rest, since it knows what the display details are - the html generator knows nothing of this.
I first learned with tables also. Getting myself to switch was hard. It was easier to go with what I knew instead of learning something new. Learning css was actually not bad and much quicker in the long run. External css & external javascript make future changes very easy.
CSS for layout and style. Tables for TABULAR data. End of story. Just ensure your documents are structured properly.
Although, I am a web developer, and my best suggestion for any amatuer photographer looking for a site, is simply go with something like zenfolio, because to do it right takes time either learning or paying someone else to do it right.
I'm a huge believer in KISS. I designed a very simple site using tables. It's not going to win any awards. People don't hire me to design websites. My site exists to link current clients to 3'rd party designed slide shows (Lightroom) and to give quick information to prospective clients. (100% of which, at this point, are word of mouth referred.)
Eventually I'll hire a qualified professional to put together something more flashy. But only when it serves me best. Tables are quick, easy, and when done with basic rules, look nice enough. All that said, CSS, if you have the time and talent, is superior.
There is a time and place for both CSS and tables. Someone viewing the site should not know whether its table or CSS based, but be able to USE the site. Usability is the issue more than the technology used to achieve it.
When HTML was young, tables and frames were the coolest kid on the block. Then frames got pimples because people had clue zero on how to code them properly - so the 'masses' turned and declared frames evil. Now the same hysteria is smearing tables. My view is that as new things come along (Ok, CS is already 10 years old), they get used to enhance the user's experience of your site. Like Shrek said, its like and onion, layers of technology working together.
To quote from Invalid's Link One above
"Tables existed in HTML for one reason: To display tabular data. But then border="0" made it possible for designers to have a grid upon which to lay out images and text."
This is so often stated as why one shouldn't use tables. And is the most stupid reason possible. It's like saying Photoshop was created for Photographers, so designers shouldn't use it.
Tables as mentioned above by Nylad can be the best solution for someone who doesn't currently do web design and isn't au fait with the numerous and hard to discover workarounds needed with CSS. The bottom line is tables work. In all browsers, identically.
Fantastic as the Zen Garden website is, a lot of the designs don't fully work in IE. Allowing them to degrade gracefully is fine, but if you can do what you want with something that works, why worry about CSS.
I considered all sorts of fancy solutions to my portfolio site when I did it a few years back and only tables could guarantee consistent + correct layout at the quality I needed at the time, without using Flash. CSS has improved since then, so now if one has time to learn CSS [not a 5 min task], then using CSS may be worthwhile. Though the principles of how a site is built up semantically is often still worth employing even if tables are being used - i.e. separate content from design. Though with portfolio sites, the content may well be the design!
troyhark, did you read the rest of the references I provided? There are many reasons not to use table other than the unsuitability for general design. Tables tend to work for standard graphical browsers, but they fail horribly at accessibility or even for just text browsers. It may be that for a photography website, assumption of graphics is acceptable, but in general, that assumption ranges from a bad idea to one that exposes you to legal action.
I did. Though the daft and irrelevent reasoning of first doesn't really encourage one to proceed further.
I actually think, long term, CSS is better, but as tables work well and consistently in Browsers and over the years have resulted in a lot of well designed sites, they are hardly unsuitable for design. Though the coding could get a little untidy it's true if you nest tables, but then if you do that then your CSS will also probably suck too. One could even argue CSS is less suitable as it is less consistent across Browsers. Interestingly one of the guys in your links admitted his table version of site worked better in more browsers than the CSS version, and had this to say "Although CSS-based design is really fast when you get used to it, you must spend a significant amount of time getting to know the rules, the box model differences, browser quirks and other theory. This comes through practice and practice only. In short: it's much easier to just use tables. If you want to make pure CSS designs, be prepared to invest time in learning. Even if you're already a seasoned developer, be prepared to hunt down bugs relentlessly, sometimes investing several hours in the process."
So if you know tables well, is it worth learning alll that extra knowledge if you aren't a full time coder?
The other site seemed to be anti CSS and more in favour of tables which is a bit odd for you to reference. !?
PS I just thought if you read books on design layout [print or web], using grids is almost certainly to be illustrated with what looks like tables, making up the page structure. So maybe tables are in fact ideal for design! ;-)
1. Learn how to use CSS (buy Rachel Andrew's book)
2. Use CSS for the general page design
3. Use tables and CSS for tabular data
There are a few CSS easy concepts to learn ; CSS is - theoretically - covering most of the designer's needs ; its proposal (selected by the w3c) is a bit weird at times imo, but, again in theory, it works.
The real problem is the implementation of CSS in browsers. It is not a "1 + 2 = 3" thing. W3c provides a theoretical language unfortunately prone to misinterpretations. To get something that works nice in both Firefox and Internet Explorer [esp. 6] is enough to drive you up the wall!
The real problem is the implementation of CSS in browsers. It is not a "1 + 2 = 3" thing. W3c provides a theoretical language unfortunately prone to misinterpretations. To get something that works nice in both Firefox and Internet Explorer [esp. 6] is enough to drive you up the wall!
It is why you need a book like Rachel Andrews's.
Do you mean 'The CSS Anthology - 101 Essential Tips + Tricks'? As I second that it is indeed a good book. But your comment also underlines the major problem with CSS, you need to learn lots of hacks and workarounds to get CSS to work with the current browsers. Which unless you want to do web design, as opposed to just building your own site, is an awful lot of work.
So if tables will easily do what you want in all the browsers, why bother to spend weeks faffing around with CSS?
Insisting that tables are only good for tabular data is as I said above, is akin to saying Photoshop is only for Photographers and not designers. It's an all too often repeated bit of nonsense, pretending to be wisdom.
This is the book.
The advices I give are based on my professional experience.
It takes some time to get used to CSS and the book helps a lot. The global design of the page and its elements gets eased a lot using CSS. Tabular data go in tables that are also subject to CSS directives.
CSS is a new dimension in designing, changing a unique line in CSS can change the whole look of your page. Like, say, "by default all tables have a border of 2 pixels" or "all paragraphs named title are font Verdana". Using CSS a page needs less instructions, and loads faster.
The problem is the browsers compatibility, this is why you need that kind of book.
