I had a client who had some input after my first prototype. Instead of going away & re-jigging the whole prototype, I opened up Firefox with the "CSS Editor" side bar and MADE THE CHANGES ON THE SPOT (with a few tweaks to the mark-up).
We achieved so much in one meeting that the client and myself were both amazed. My guess is about 2-3 meetings worth of changes and iterations in less than 2 hours. The client was able to SEE changes and assess them in realtime.
If you're quick with basic CSS layout, I can 100% vouch for CSS/XHTML based prototypes/mock-ups/wireframe hybrids.
On 06/08/2004, at 4:40 AM, Ian Fenn wrote:
Hello,
I'm in the process of redesigning a website. My client wanted something to
show internal stakeholders so I started doing a few wireframes but suddenly
wondered, "Why am I doing this? Why don't I just build the website using web
standards?"
A day later I finished a working prototype of the website in question. The
client is happy but another producer has been quite vocal with his opinion
that the prototype was built too early.
From my perspective, a prototype has more value than wireframes. Web
standards make development much more rapid, so we can respond quickly to any
other needs thrown up before going into production.
What do you think?
--- Justin French http://indent.com.au
*****************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*****************************************************
