Saturday, July 17, 2010

When One Word is More Meaningful Than a Thousand

Quite a bit to digest for us web design novices, but some interesting stuff nonetheless. I found the following passage interesting in light of the way I approached building my Jump Page:

"I know that many people like to mix wireframing, HTML and even design into one organic and homogeneous process. The downside to this is that you will have a hard time not compromising your work. When you’re designing, writing HTML and CSS is not priority number one; and once the design is done, you’ll find it tough to go back and rework your code to match HTML and CSS standards.

It’s also refreshing to try to build a website based purely on a set of wireframes, without the slightest notion of design. It helps you focus on meaning and makes it easier to spot components that are actually the same but could differ wildly design-wise. And if you’ve done it right, you’ll find that during CSS development, you don’t have to adapt the HTML at all, unless the design calls for major structural changes.

Try to build your HTML templates based on wireframes, and save the design and CSS for when your static HTML templates are completed."
Read the full article

1 comment:

  1. Hmmm...I know they're the experts, but I'm not so sure I agree with this approach. Good planning (which IS in fact the wireframe stage) should always take into consideration, though perhaps not yet illustrate it, the aesthetic design plan as well. I understand basic HTML content will consist primarily of the "structure"; however, often times it WILL need to re-structured or modified according to desgin treatments implemented in the CSS coding stage.

    Interesting indeed, Dylan. Thanks for sharing. have I lost 'ya yet?