Quote:
Originally Posted by fartfly
designer = yes
web designer = yeah, if you still live in 1998 ( chopping up a jpg and calling it a website  <-- 2008? ) ack ack ack
I think you should use what gets the job done. If the W3C isn't paying your bills I wouldn't go out of my way to make everything compliant. You should strive to make things as efficient as possible ... easy to update...
the trick is doing that and making it look good at the same time across browsers.
a good web "designer" ...
1. Creates something that is easy to update. ( not loads of shit code --->one reason css was developed to reduce that<---)
2. Easy to navigate.( not letting your ("I have this really different and great design idea" <--- that hinders usability)
3. Makes the client happy. ( if a blocky css design turns him/her/it on and gets the job done so be it ... ) |
In a perfect world...
You have a Graphics Designer that works well and can communicate well with the Web Designer.(does that happen?)
As a team they work together Optimizing the Design and the Code, give and take until they have something that looks good, usable and easy to update.
Usually that doesn't happen. The Graphic Designer and the "Code Geek" can't get along...and great ideas are lost in translation. When you have a guy doing both you're usually missing out on key things in both areas.