CSS means Constantly Sickening & Stupid!! — OZONE Asylum, home of the Mad Scientists

CSS - DOM - XHTML - XML - XSL - XSLT

CSS means Constantly Sickening & Stupid!!

This page's ID: 28869

Edit Post

Who can edit a post?	The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.

Your User Name:
Your Password:
Login Options:	Remember Me On This Computer

Your Text: Insert Slimies » Insert UBB Code » Close Last Tag \| All Tags UBB Help	Hi Rob; Sorry to be absent from this really interesting discussion. Great comments in this thread so far. I've got some thoughts of my own. First: there are at least three really important disciplines in today's web design (four if you count sales/marketing, but let's not go there): the content people whose job it is to provide meaningful content the developers who make the technology work the designers whose focus is on appearance It's REALLY hard to do all three by yourself. You I gather come from the design spectrum. You start out with an idea of what the page is going to look like and work from there. The internet started out as a convenient means of distributing primarily text with an odd illustration or chart here and there. Then it took off commercially and there was a huge push to make a web page look like a print brochure or catalog. Maybe it's my own bias, or the blogs I follow, but now things have swung towards a more "semantic" web, where (to the extent possible) everything in the html markup means something. All the presentational stuff is handled by css. What does that mean? If you look at your page without any css (except the browser's default styles) does it make sense? Does it look like an outline? If you were a googlebot would you know what the purpose of the page was? This article by Tommy Olsson was a real eye-opener for me: http://www.sitepoint.com/print/html-37-steps-perfect-markup In a nutshell - people have bought that "tables for presentation are bad", but they have substituted divs which are essentially equally meaningless. Tommy advocates using html elements wherever possible and styling them. Sometimes you need a div and sometimes a div is semantically meaningful (a division), but use html elements wherever they exist. If you can find a used copy of Andy Clarke's "Transcending CSS" I REALLY recommend it. I say "used" because 2/3 if it is pretty esoteric. But there is some terrific material on how to start the design process, and how to mark up a page FIRST and style it LATER. That puts the emphasis solidly on meaning, plus it provides GREAT flexibility for re-styling later. It's less fragile, less built around one design. Loading...
Options:	Enable Slimies Enable Linkwords

« Backwards — Onwards »

Show Forum Drop Down Menu