Web design as it is today owes a lot to a physicist at CERN in 1980, Tim Berners-Lee, who had an idea for a system for using and sharing documents. That system became HTML in 1990.
From the beginning of the 90′s till circa 1997, Web Design was a concept very vaguely and broadly defined (Kotamraju 2002) to include a vast skill set needed for the technical process of creating and maintaining a website. The study by Nalin Kotmaraju to pin down a definition of Web Design and list the required skill set was published in 2002. Ten years later, her findings from the 90s (She conducted both quantitative and qualitative extensive market and informant research) still resonate. Web Design is still a vague and all-encompassing concept and Web Designer is still what employer and worker agree it to be.
However, three general sub-specialties are becoming more mainstream: Graphics Production, Authoring and Media Development (Niederst 1999).
Graphics Production comes closest to ‘traditional’ Graphic Design (creating mockups, images, choosing typography etc…) Authoring and Media Development now both fall under Front-End Development (requiring considerable knowledge in both scripting and design, translates mock-ups to the client-side part of a website). A third category of specialists are usually needed to complete the process of a website creation. These ‘back-end’ (lol) programmers are responsible for the ‘plumbing’ of the website such as databases and server-side programming, however these programmers are so far up the Computer Science technical tree that they have been non-players in the turf war between Computer Science and Graphic Design over Web Design.
At first, the Code dominated the Art. HTML was unwieldy and the web denied designers control. At one point WYSIWYGs gave back designers control and put the code in the background, but all that changed with the introduction of more powerful versions of HTML and of the Cascading Style Sheets (CSS) that would make website maintenance and stylistic updates a breeze. The market required ‘code-created’ websites again.
Entering 2013: A synergy of Code and Design have never been more important than now. With the widespread use of devices with wide ranges in resolutions (iphones, tablets, high-res descktops, giant screen TVs that can surf the Internet) there is a need for responsive websites at the very least; sites that re-size and re-flow to present coherent, legible, pleasantly presented content on any screen. There are even talks on the blogs of the need to design ideal device-agnostic websites (Patrick Cox: Becoming Device Agnostic, Sarita Harbour: The Device-Agnostic Approach to Responsive Design, Thierry Koblentz: Device Agnostic Approach to Web Design) that would stand the test of time and of future resolutions.
Device-Agnostic Design is a fluid, non-linear process requiring the front-end programmer to design as he/she writes code, guided by trial and error and the moment by moment ‘flow’ of the layout on a constantly re-sized test browser.