Previous Message
Next Message

HTML/CSS development process

Sent by Chris Price on 10 December 2004 18:06


> there is much of 
> value in print visual design for web designers

I moved over from design for print to web design.

I think one of the big differences with the two is that in design for print,
it doesn't matter to the end user how you built the page as long as the
printer can match your proof.

Building a web page is like sending your disk to 20 different printers each
with a different type of printing machine, image setter, font library and
inks.

But I do think that good practice is transferable. In design for print I
came to rely heavily on styles. In doing so, a lot of time could be saved by
incorporating style tags in the text so that when it was imported into the
DTP application everything was automatically in the right font at the right
size etc.

Separating style from content in web design has the same advantage. Its
interesting that for many years Quark has spent vast resources in developing
XML and work flow in its applications.

I think its down to knowing why you do what you do. Someone who understands
the workings of Quark and why its so powerful will instinctively latch on to
style sheets and XHTML. Anyone who thinks you change the weight of a
typeface by pressing bold just doesn't understand.

-- 
Chris Price

Choctaw

[EMAIL-REMOVED]
http://www.choctaw.co.uk

 

______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Previous Message
Next Message

Message thread:

Possibly related: