On 26 Sep 2005, at 10:11 AM, kvnmcwebn wrote:
Do most wsg members - who do both the design and mark up - actually go
to
code when the design is done without looking back?
I try but alway end up going back and forth to make improvments. It
eats
time.
This is probably the biggest benefit of the whole web standards
process for
me, i mean the time it saves when i decide to change something after
im 30
pages into a site.
I guess part of my question is when do you know the design is there
from a
wsg point of view?
Is it when you know the client will go wow that looks nice?
maybe this is o.t. and too subjective a topic
No, I don't think it's OT. To qualify my tongue-in-cheek comment about
a cheque - design is not a static process. It's a continuum. And with
this medium in particular, unlike print where sooner or later a
commitment has to be made, the design process carries right into
production. Many clients will continue to request changes as they 'live
with' the designs we supply, and coding to Standards, as you say, makes
incorporating those changes much, much easier - regardless of what
stage of development a site is at.
That's not to say we shouldn't charge for those changes, of course.
Careful control of 'scope creep' and a clear agreement about what
constitutes author's corrections should always be in place...
N
___________________________
Omnivision. Websight.
http://www.omnivision.com.au/
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
