Friday, February 23, 2007

Are you Torn between the Users Point of view and the Coders Point of View? Here are some Amazingly S

Most of the Web Designers presently come from the artistic background. They think in the pictures not in the code. The basic semantic of designing a page is using the HTML and CSS crudely. This is all which is used to arrange the boxes in the web page unknown to the true nature of the box itself or what it contains. Altering that strictly visual mentality is the highest hurdle to overcome when a graphic designer first dives into semantics and web standards. FOR the visual designer, really understanding web standards means you'll have to change the way the web designers think about the design. To grasp something is to achieve a deep, intuitive comprehension of it. To truly "get" web standards, you have to understand them as more than a means to an end, more than simply an alternative method of producing a visual design.

One can't channel your creative energy solely into the appearance of your web pages without thinking about their underlying structure. So to be a designer a person must diversify his approach to design problems. He must become equal parts of a coder and writer who writes the content to the site. They also learn what can't be accomplished easily with CSS and, will spot those obstacles early on and adjust your design accordingly. Every medium has its limits and any designer learns to embrace those constraints, using the medium itself as yet another outlet for creativity. Thinking like a viewer will help you find creative solutions to visual problems. Designers demands creative problem solving, and though suggests a slightly different angle of attack, the target remains the same. Cultivate these aspects of your personality, giving each one independent attention.

Try starting with an outline of your content before the need to even doodle first thumbnail. List everything that will eventually be displayed on the page, from logo to copyright notice. Group related things together in meaningful portions. Take the time to understand the content, even if that means actually reading it. Understand the ideas that communicating and will be better prepared when you start drawing it out. Then the designers can go on to arrange those chunks of information into a visually appealing design, plan the sequence of elements in your markup and which CSS properties will be using to affect their presentation.

Molding the web experience through pristinely valid, semantically rich markup and elegant CSS will come to you as easily as breathing. The old presentational methods will feel awkward and distasteful, primitive in their crude brutality. If one view the source of a site built a year ago and cringe in embarrassment, wondering how could ever think such sloppy, unintuitive spaghetti code was remotely acceptable.

When the designers will understand that content and code really do matter at least as much as design, they will become a better designer in the end and grasp web standards.


Source: http://www.a1articles.com