website comps

[Gregory]

What is your preferred method for creating website comps to show to a client? Do you create a static layout, for example, in Photoshop? Or do you make something that they can view in a browser?

I have just been learning a bit about Fireworks CS3, and I see that there are some methods for quickly creating rollovers and drop down menus. I am trying to decide whether it's worth the effort to do this for our first round of proofs. But maybe I'm, once again, making things overly complicated, which is my forte.

Thanks for any feedback/advice.

[Savvywebdesign]

First round of proofs, for me, is always a static image. Clients are so likely to request changes that I don't believe it's worth the effort to make up working pages for first drafts.

An exception would be in the case of demonstrating some effect that the client might not grasp without seeing it in action. At the moment I can't think of an example of any such effect, so hopefully you know what I mean. :)

[Gregory]

Thanks, Savvy. Do you make prints for your clients, or do you show them something on screen? Maybe it doesn't matter as long as the design is still static?

[Benjamin]

I often create a 'mock webpage' which is an image set inside an HTML page, set up so that centering works properly. This allows the client to see the page inside a browser, in its real context, but is very quick to do. Obviously no links or buttons would work, so you need to explain to the client what exactly it is.

[emmerse]

I too, create spec pages with one big jpg horizontally centered and the background image or color in place. Quick, easy and more accurate than printing a spec.

[jibble]

i RARELY touch html(or the like), but flash is my thing and it's next to impossible to explain things to a client about flash and "how it will animate." Typically we start with a series of static images for a few sections(not all sections, but a general idea of a few sections) so they can get a feel of how it will look. For flash and animation, we set up a password protected section(no need really but clients love it cause they feel its "safe") on the backend of their server with the actual working site AS WE GO. Some will probably say this is a no-no but the last thing i want to do is a ton of flash work and have it rejected, so i let the client view it as we build it so they can catch things they don't like immediately, preventing hours of worthless actionscript and animation. Also, this way they can see the progress and give input appropriately. It's a good way of keeping them involved as well as keeping them up to speed on whats going on. Also, we try to tell them right off the bat that the results are generally going to vary from the comps(with flash anyway). It's up to you how to set it up, after a few sites you'll get a routine down and it's cake from then on really.

[Savvywebdesign]

Thanks, Savvy. Do you make prints for your clients, or do you show them something on screen? Maybe it doesn't matter as long as the design is still static?
It's always on-screen, almost always emailed to them. I don't think making prints would serve any purpose. I don't believe prints would appear any more professional or "official".

Luckily all of my clients so far have had access to a computer. Even with the use of printed proofs, producing a website for a client without computer access would be a potential nightmare. :)