I first read about this two
I first read about this two years ago in an Andy Clark book. Then it seemed crazy, now is looking more and more like a, somewhat, good idea that warrants further testing. I can see how using the browser to develop is a great idea. Photoshop or Fireworks prototypes dont always look the same in a browser as the client saw them in an image file. The web renders things differently. On the other hand, graphic intensive designs cant be simply edited in a browser either.
So, what I would do is...
1. write the html
2. build a prototype for me to use that the client never lays eyes on.
3. create the graphics in PS. Create additional graphics for things the client might want (buttons, icons, starbursts).
4. show the client you're first idea in the browser. make client presentational requests right there in front of them with firebug for FF, or Firebug Light for Chrome.
5. If the client wants to add extra graphics, you have some with you.
No more prototype back-and-forth until the client is happy. make the changes right then, and save time and money! Its a good idea to build a little toolkit that holds misc graphics and snippets of code you might need during the client meeting on design, or whatever.
I think its a great idea, but will only work if you are an organized person with a good toolkit to work from. My toolkit will include all the new css3 stuff, a nice mixture of RGBA color values, misc graphics, snippets of code, whatever i need to build a website.
I've been doing this stuff
gary.turner wrote: I've been
I've been doing this stuff for coming on ten years, and have never used a mock up image.
Ive been doing css for 2 years. Maybe I'm a little late jumping on the wagon.
I tend to get a PSD from
I tend to get a PSD from client.
I look at it in code, not design.
I figure out what will be divs, lists, paragraphs, etc...
Without touching the PSD I code the site as it should be and then take the elements as needed and place them into the CSS.
Only adding additional HTML as required if I underestimated the way something is laid out.
I know you're supposed to "code" before you "design". But I usually just look at a design as it should be coded and alter the PSD if there is something that is just ridiculous.
I've just begun the (what
I've just begun the (what will no doubt be a long, drawn-out) process of redesigning my site. I'm starting with reviewing the content and structure of my current site, editing it, and writing any new content that is required. I'll then be marking up the pages and intend on trying designing in the browser - to at least see how I go. I'm keeping lots of notes as I go through the whole process this time and hope to write a post or series about the experience.