At the Blue Flavor blog, Nick Finck casts another vote for making XHTML wireframes. I have to admit I find this idea appealing. Granted (and he grants this himself), it may not be the right approach for every client, but the prospect of creating blueprints and schematics that don’t get thrown away after they’re approved but that actually help give the web developers a leg up, is mighty appealing:
So why? Why would we want to do XHTML wireframes? Wouldn’t it take more time to do them in XHTML than it would in Visio or something? Well, yes and no. Yes, you would have to code the XHTML, but that would need to be done at some point anyway. Yes it may seem like it’s slower to create wireframes in XHTML but once you have done your first website using this method a lot of the same markup can be repurposed especially when it comes to navigation and various methods of displaying information on a page like multi-column lists and so forth. In the end it’s actually more efficient to be building wireframes in XHTML and even navigation schemas because you can see exactly how it works and you only spend the energy necessary to create it once, not twice (once in Visio and once in XHTML).
(via Thomas Vander Wal)
Leave a comment