|
|
Posted by Ed Seedhouse on 12/04/06 01:05
On Mon, 04 Dec 2006 00:01:20 GMT, Ikke <ikke@hier.be> wrote:
>Hi everybody,
>
>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.
All this and not a word about the content! Do people use a website
because it looks cool or because it has content they want or need? I
suggest it is the latter and if I am right then you have your design
process rather backwards, don't you?
How about this. Start with the content you want to give to people.
Split it up into page size chunks. Now take the first chunk and mark it
up with html according to it's meaning - that is, to use a chatch word,
"semantically".
Don't style it at all yet, just code it semantically and take a look at
the result in a browser. Then think about how the content will best be
laid out to make it most useable to the user. Remember all the things
you don't have any control over, that some people possibly will use your
page yet never see it, and that the web is not paper.
Now create any html hooks you need for your CSS, such as grouping
elements and so on, then code your CSS to achieve the layout you decided
will best server your users and make it look good.
Just for your consideration...
Navigation:
[Reply to this message]
|