Comments on: A Guide to Wireframing

By: brian mcdermott

brian mcdermott — Sun, 16 May 2010 05:49:36 +0000

Wow, great post guys!

As a newbie to web design, and with a few new web projects on the horizon, this article alleviates a lot of the anxiety I was having about “where do I start?”

I wonder though, 1) is it necessary to wireframe every single page that will exist throughout the site? — and 2) do you present a few various wireframe options to illustrate possible layoutsâ€”along with all subsequent wireframe pages? OR would you present, say, 2 or 3 home page wireframe layouts to the client, and then based on their feedback, flesh out the remaining wireframe pages of the chosen direction? I hope this makes sense.

Thanks!

By: Dan

Dan — Fri, 12 Mar 2010 21:19:36 +0000

I love the pen and paper suggestion. It’s so tempting to simply open up a browser, or photoshop, and go to work, but I’ve found that stepping away from the laptop can offer new design perspectives.

By: George

George — Tue, 02 Feb 2010 16:20:26 +0000

Nice post. I completely agree – #2 pencil first, then once the underlying structure and some sense of the navigation is drawn out – move to a functional mockup system. The one that I’ve really fallen in love with is FlairBuilder – which just keeps getting better (and even imports Balsamiq files!).. Mockingbird looks very interesting as well.
The whole process really helps solidifying the navigation, content needs at each stage, and the overall look and feel – prior to really writing a lot of code.

One thing that would make the system complete is a way to move directly from functional mockup to a CMS… maybe the folks at Joomla or Drupal could figure this transition out.

By: This Weeks Twitter Design News Roundup N.21 - Speckyboy Design Magazine

This Weeks Twitter Design News Roundup N.21 - Speckyboy Design Magazine — Tue, 26 Jan 2010 08:58:27 +0000

[...] A Guide to Wireframing [...]

By: Kevin Mist

Kevin Mist — Sun, 24 Jan 2010 21:15:43 +0000

I have never had much luck with the computer versions of the wireframe. I guess I am an old guy (relative to this business) but I still like using the number 2 pencil on a piece of notepaper for mine. I typically do each unique page although I will admit to having skipped this (and regretted it later)

Nice post. Keep up the good work

By: links for 2010-01-19 « Boskabout

links for 2010-01-19 « Boskabout — Tue, 19 Jan 2010 18:05:29 +0000

[...] A Guide to Wireframing | Papermashup.com Planning a project thoroughly is often more important than the design, app or site. If a project is badly planned and organised then your heading for a disaster. [...]

By: John Rockefeller

Mon, 18 Jan 2010 23:18:51 +0000

Wireframing makes a lot of sense on large-scale projects. But if you’re coding something small, it’s typically better to do it Agile. BTW: There is a grammar mistake in this article. The “your” in the first paragraph should be “you’re.”

By: Andre

Andre — Mon, 18 Jan 2010 19:03:46 +0000

Another wireframing tool I find very useful (used it on my last project) is http://gomockingbird.com/ . No flash required, pretty nifty.

By: Ashley

Ashley — Mon, 18 Jan 2010 16:17:16 +0000

@Matt, thanks. that’s exactly what i wanted to communicate

By: Matt Zillhardt

Matt Zillhardt — Mon, 18 Jan 2010 15:54:17 +0000

Excellent article. Its nice to see a clear defined reason behind wireframing that you can easily communicate with management. Most of the time management / clients want to see something right away and don’t understand the necessity of wireframes.