|
|
Posted by K A Nuttall on 12/04/06 07:38
Ikke wrote:
> First of all: I am a software developer, not a designer. When I
> start designing a website, first of all I list the things that
> need to be shown. Then I surf around for a while, looking for
> ideas, color combinations, layouts, etcetera...
>
> After all that, I start writing html/css and keep on altering what
> I have until I end up with a design I like.
>
> At my previous workplace, the designers always started out in
> Photoshop, creating the site until all the details were finished,
> after which they handed the result to the developers.
>
> I'd like to know which method people prefer, or if there are other
> ways of handling the design process.
I'm a web site developer, and general techie. Where I work, 'concepts'
are sold to the customer. They are shown rough alternative designs,
created in Photoshop, together with wireframe storyboards and site
maps. A developer provides a verbal overview of the operation.
Usually, the customer knows very little (if anything) about cross-
agent, semantic markup and accessibility issues, but will gladly take
our word that these are things to be concerned about.
Once the content, structure and style are agreed upon. The job is
passed to the graphic designer, who has limited experience of web site
development, and has learned what is 'good' and what is 'bad' from
having to redo things when asked. At the same time, content and
specific images are harvested from the customer and stock libraries.
It is only when most of this has been done, that the job is passed to
the end developer. This is more through necessity than by choice. I
personally would like to be involved at an earlier stage, but I can
appreciate why I am not (too many cooks). However, being the last in
line, I am endowed with a certain amount of 'carte blanche', after all,
the designs are only 'concepts'.
I look at the content and the design, and come up with a sensible
markup and navigation strategy, then incorporate the suggested style as
best I can, without sacrificing meaning and usability.
I'm not saying it's the best way to do things, but it's the way I work
at the moment, and this has been forced by commercial reality rather
than academic desires.
--
K A Nuttall
www.yammer.co.uk
Re-type the e-mail address how it sounds, remove .invalid
Navigation:
[Reply to this message]
|