Web design is part of starting a website (web development) which can include web server configuration, writing web applications and server security.
History
Tim Berners-Lee, the inventor of the World Wide Web published a website in August 1991, making him also the first web designer. His first was to use hypertext with an existing email link.
Early on, websites were written in basic HTML, a markup language giving websites basic structure (headings and paragraphs), and the ability to link using hypertext. This was new and different to existing forms of communication - users could easily open other pages.
As the Web and web design progressed, the markup language used to make it, known as Hypertext Mark-up Language or HTML, became more complex and flexible. Things like tables, which could be used to display tabular information, were soon subverted for use as invisible layout devices. With the advent of Cascading Style Sheets (CSS), table based layout is increasingly regarded as outdated. Database integration technologies such as server-side scripting (see CGI, PHP, ASP.NET, ASP, JSP, and ColdFusion) and design standards like CSS further changed and enhanced the way the Web is made.
The introduction of Macromedia Flash into an already interactivity-ready scene has further changed the face of the Web, giving new power to designers and media creators, and offering new interactivity features to users. Flash is much more restrictive than the open HTML format, though, requiring a proprietary plugin to be seen, and it does not integrate with most web browser UI features like the "Back" button.
Issues
As in all professions, there are arguments on different ways of doing things. These are a few of the ongoing ones.
Liquid versus fixed layouts
Programmers were the original web page designers in the early 1990s. Currently most web designers come from a graphic artist background in print, where the artist has absolute control over the size and dimensions of all aspects of the design. On the web however, the Web designer has no control over several factors, including the size of the browser window and the size and characteristics of available fonts.
Many designers compensate for this by wrapping their entire webpage in a fixed width box, essentially limiting it to an exact pixel-perfect value, which is a fixed layout. Some create the illusion of liquidity by building the graphics for their webpage at a size larger than any current standard monitor size. Other designers say that this is bad because it ignores the preferences of the user, who might have their browser sized a specific way that they like best. These people propose a liquid layout, where the size of the Web page adjusts itself based on the size of the browser window.
There is a usability reason (rather than wanting control) for why a designer may choose a more fixed layout. Studies have shown that there is usually an optimal line width in terms of readability. One rule to appear from such studies is that lines should be between 40-60 characters long, or approximately 11 words per line. But users may choose their windows size and font selection to optimize other factors more important to them.
This decision of which style of layout to use is often made on a case by case basis, depending on the needs and audience of the website.
In some cases, it is difficult to create fixed layouts which work well given the amount of content needed, and the fact that one has to try to cater for the needs of all prospective users.
Flash
Macromedia Flash is a proprietary, robust graphics animation/application development program used to create and deliver dynamic content, media (such as sound and video), and interactive applications over the web via the browser. It is not a standard produced by a vendor-neutral standards organization like most of the core protocols and formats on the Internet.
Many graphic artists use Flash because it gives them exact control over every part of the design, and anything can be animated and generally "jazzed up." Some application designers enjoy flash because it lets them create applications that don't have to be refreshed or go to a new web page every time an action occurs. There are many sites which forego HTML entirely for Flash.
Flash detractors claim that Flash websites tend to be poorly designed, and often use confusing and non-standard user-interfaces. Up until recently, search engines have been unable to index Flash objects, which has prevented sites from having their contents easily found. It is possible to specify alternate content to be displayed for browsers that do not support Flash. Using alternate content also helps search engines to understand the page, and can result in much better visibility for the page.
The most recent incarnation of Flash's scripting language (called "actionscript", which is an ECMA language similar to JavaScript) incorporates long-awaited usability features, such as respecting the browser's font size and allowing blind users to use screen readers. Actionscript 2.0 is an Object-Oriented language, allowing the use of CSS, XML, and the design of class-based web applications.
The final consensus is that Flash is simply a tool, and like all tools it takes a skillful craftsperson to know when, and how, to use it properly. Macromedia's other two products, Fireworks and Dreamweaver, makes Flash integration with graphics and HTML a lot easier.
CSS versus tables
Back when Netscape Navigator 4 dominated the browser market, the popular (but now deprecated) solution available for designers to lay out a Web page was by using tables. Often even simple designs for a page would require dozens of tables nested in each other. Many web templates in Dreamweaver and other WYSIWYG editors still use this technique today. Navigator 4 didn't support CSS to a useful degree, so it simply wasn't used.
After the browser wars were over, and Internet Explorer dominated the market, designers started turning towards CSS as an alternate, better means of laying out their pages. CSS proponents say that tables should only be used for tabular data, not for layout. Using CSS instead of tables also returns HTML to a semantic markup, which helps bots and search engines understand what's going on in a web page. Today, all modern Web browsers now support CSS with different degrees of limitations.
However, one of the main points against CSS is that by relying on it exclusively, control is essentially relinquished as each browser has its own quirks which result in a slightly different page display. This is especially a problem as not every browser supports the same subset of CSS rules. For designers who are used to table-based layouts, developing Web sites in CSS often becomes a matter of replicating what can be done with tables, leading some to find CSS design rather cumbersome. For example, it is rather difficult to produce certain design elements, such as vertical positioning, and full-length footers in a design using absolute positions.
These days most modern browsers have solved most of these quirks in CSS rendering and this has made many different CSS layouts possible. However, people continue to use old browsers, and designers need to keep this in mind. Most notable among these old browsers are Internet Explorer 5 and 5.5 which, according to some web designers, are becoming the new Netscape Navigator 4 ? a block that holds the internet back from converting to CSS design.
How it Looks vs. How it Works
Since so many web developers have a graphic arts background, they often pay more attention to how a page looks, without considering how visitors are going to find the page. On the other side of the issue, search engine optimization consultants (SEOs) obsess about how well a web site works: how much traffic it generates, and how many sales it makes. As a result, the designers and SEOs often end up in disputes where the designer wants more 'pretty' graphics, and the SEO wants lots of 'ugly' keyword-rich text, bullet lists, and text links. Another problem when using lots of graphics on a page is that download times can be greatly lengthened, often irritating the user.
Web Design & Development
Many organizations are interested in building web applications for their business but are unaware of the various steps that are needed to build a compelling web application. In this article I will attempt to put together the various pieces of the puzzle. Application development involves several distinct efforts that need to come together to build a compelling end product. A compelling end product is the combination of design, development architecture, development implementation, automated regression and functional testing and performance and load testing.
Design: People often confuse design with development. Moreover even within design, user interface design is often confused with graphics design. Web user interface design involves the design of the flow of the website and the layout of the specific web pages within the website. The web user interface designer concentrates on the usability of the application. The user interface designer will typically develop "wireframes" using tools like Adobe Photoshop to convey the design. These are often initially developed as prototypes and usability testing is carried with user groups out to ensure that the web application will be intuitive and easy to use. Graphics design on the other hand relates to the aesthetics of the page. The graphics designer is responsible for the aesthetic layout of the pages and the creation of the various graphical objects inside the pages such as images and flash objects. The graphics Designer will typically use a combination of tools such as Adobe Photoshop, Adobe Illustrator and Adobe Captivate to create the actual graphics objects. A designer will need to work closely with other groups to make sure the design process does not compromise the performance of the application by making sure that the graphics objects are small thus ensuring that the various web performance metrics are unaffected.
Development: This involves converting the design into an actual application. The development typically involves an architectural phase where the underlying modules that make up the application are scoped out. If persistent data storage is needed, a database schema should be designed to accommodate the data storage needs. The choice of the operating system (e.g. Windows, Linux or Solaris) where the web application will run, the web server (e.g. Microsoft IIS, Apache or Tomcat) which will run the web application and the back end database (e.g. Microsoft SQL Server, Oracle, MySQL or Postgres) which stores the data will need to be made. Various development frameworks are available to build web applications. The most common ones are ASP and ASP.NET from Microsoft, Java Servlets and JSP from Sun, PHP and Perl that are open source. The choice of the application framework is typically dictated by the strengths of the members of the development team. The architectural phase is followed by the implementation phase. This is typically the longest part of the project and during this phase the actual code is written using the design specifications and graphics objects developed by the design team. The programming will typically be done using a combination of the application frameworks mentioned earlier together with HTML, JavaScript and CSS style sheets.
Quality Assurance and Testing: A surprising number of people are of the view that quality assurance and testing is desirable but is not actually needed. Unfortunately this view has its roots in total ignorance of the process that is needed to build a good end product. Regardless of how pretty or slick we make the application, if it does not work as expected, users will reject it. Quality assurance and testing involve two different kinds of tasks. Functional and regression testing is used to verify that the developed application is doing what it is supposed to do. This is achieved by test automation using a functional testing tool. Load and Performance testing is used to ensure that the application performs as intended when it is subjected to the typical load of a production environment. Load testing is practically speaking impossible to perform without using an automated load testing tool since it involves the simulation of a large number of concurrent virtual users. This effect cannot really be achieved manually and needs the assistance of an application that is designed to subject the application to a specified load and then measure its performance when it is subjected to that load. Quality Assurance teams will need to track the bugs or defects in the application using bug tracking tools. Such tools will allow defects to be tracked by all members of the team.
The three groups mentioned above tend to be specialized for their skill set. As an example, people often make the mistake of using developers as quality assurance testers. This is not a wise strategy because most developers who are good at writing software are quite poor at finding bugs or defects in their own software.
Writing good and compelling web applications requires an understanding of all phases of the process, design, development and quality assurance. Skipping phases or taking shortcuts will result in low quality software that will generally cost more in the long run.
Both Mar & Umair Khan are contributors for EditorialToday. The above articles have been edited for relevancy and timeliness. All write-ups, reviews, tips and guides published by EditorialToday.com and its partners or affiliates are for informational purposes only. They should not be used for any legal or any other type of advice. We do not endorse any author, contributor, writer or article posted by our team.
Mar has sinced written about articles on various topics from Food and Drink, History and Software. Related pages: , ,. Mar's top article generates over 673000 views. to your Favourites.
Cheap International Airfares From These tips and others will help you in selecting the right deal at the right time in order to save a great deal of money on airfares