Web Design, Web Development

Choosing the right web design company for your website design project.

You’ll find numerous website design agencies to choose from, therefore it’s essential to choose one that is going to be perfect for you and your business. A website designer can do more than simply construct a couple of pages based on your brief. They’ll help you  produce a website that should best suit your visitors. Aside from creating the  ‘front end’ of your website, services that website designers can provide include things like:

COPYWRITING

Ensuring that the text and photographs on your website catch the attention and engage site visitors. Correctly translating your brand to the web making certain that the values and personality of your business come across loud and clear.

REDESIGNING YOUR CORPORATE IDENTITY

or assisting you to create one, if this is something you don’t have already.

SEARCH ENGINE OPTIMISATION

Ensuring that your website ranks high up in search results. Choosing a search engine optimisation services allows you to optimize the content of your site to ensure that it shows up prominently in search results.

BESPOKE WEB DEVELOPMENT

This will likely include things like content management system and e-commerce solutions.

Your budget as well as the scope of your project will certainly  determine what services you will require, plus it’s important to clarify these   together with your selected web design company right away.

When setting up a shortlist of website designers you can consider web sites that appeal to you, they don’t have to represent your market, and see who’s created them; in most cases this is indicated  in the footer area of the website.

Website designers of all sizes with satisfied customers will have their work presented on their own web sites. This can be the best indicator of whether the agency will have the ability deliver the results, however do make certain they were sufficiently involved with that site’s development. Once you have put together a list  of website designers, you can then  ask them to provide you with a web design proposal  that will allow you to decide if the agency will fit your company.

Usually, it’s been highly recommended for companies to put detailed requirements together prior to hiring a designer. However  many businesses won’t always realize what they or their potential customers are looking for, even if they believe they do.

If you run into problems when choosing website designer, you can contact  OMdeSIGN.  Remember, we are experts in web design and web development.

Advertisements
Standard
Uncategorized

The history of the Internet and the web, and the evolution of web standards

Introduction

“Where shall I begin, please your Majesty?”

“Begin at the beginning,” the King said gravely, “and go on till you come to the end: then stop.”

Alice’s Adventures in Wonderland; Lewis Caroll

Everything has to begin somewhere, so our journey will start with a focused history lesson. Below I am going to give you a brief overview of the creation of the Internet, the World Wide Web, and the “web standards” that this entire series focuses upon. I think it is useful and interesting to understand how we got to where we are, but it will be short enough so you don’t get overwhelmed, and can get into the details nice and quickly. If any terms are unfamiliar to you, don’t worry; if they’re important for learning web development they’ll be defined in the later articles that go into more depth on each subject, and you can always Google them! If you are already familiar with the history of the Internet or the World Wide Web, feel free to skip to the section on web standards.

The article contents are as follows:

  • The Internet’s origins
  • The creation of the world wide web
  • The browser wars
  • The coming of web standards
  • The formation of the W3C
  • The web standards project
  • The rise of web standards
  • Summary

The Internet’s origins

On the fourth of October in 1957 an event occured that would change the world. The Soviet Union successfully launched the first satellite into Earth’s orbit. Called “Sputnik 1″, it shocked the world—especially the United States of America, who had their own programme of satellite launches underway, but had yet to launch.

This event lead directly to the creation of the US Department of Defence ARPA (the Advanced Research Projects Agency), due to a recognised need for an organisation that could research and develop advanced ideas and technology beyond the currently identified needs. Perhaps their most famous project (certainly the widest used) was the creation of the Internet.

In 1960, psychologist and computer scientist Joseph Licklider published a paper entitled “Man-Computer Symbiosis”, which articulated the idea of networked computers providing advanced information storage and retrieval. In 1962, whilst working for ARPA as the head of the information processing office, he formed a group to further computer research, but left the group before any actual work was done on the idea.

The plan for this computer network (to be called “ARPANET”) was presented in October 1967, and in December 1969 the first four-computer network was up and running. The core problem in creating a network was how to connect separate physical networks without tying up network resources for constant links. The technique that solved this problem is known as packet switching and it involves data requests being split into small chunks (“packets”,) which can be processed quickly without blocking communication from other parties—this principle is still used to run the Internet today.

This concept received wider adoption, with several other networks springing up using the same packet switching technique—for example, X.25 (developed by the International Telecommunication Union) formed the basis of the first UK university network JANET (allowing UK universities to send and receive files and emails) and the American public network CompuServe (a commercial enterprise allowing small companies and individuals access to time-shared computer resources, and then later Internet access.) These networks, despite having many connections, were more private networks than the Internet of today.

This proliferation of different networking protocols soon became a problem, when trying to get all the separate networks to communicate. There was a solution in sight however—Robert Kahn, whilst working on a satellite packet network project for ARPA, started defining some rules for a more open networking architecture to replace the current protocol used in ARPANET. Later joined by Vinton Cerf from Stanford University, the two created a system that masked the differences between networking protocols using a new standard. In the publication of the draft specification in December 1974, this was called the “Internet Transmission Control Program”.

This specification reduced the role of the network and moved the responsibility of maintaining transmission integrity to the host computer. The end result of this was that is became possible to easily join almost all networks together. ARPA funded development of the software, and in 1977 a successful demonstration of three different networks communicating was conducted. By 1981, the specification was finalised, published and adopted; and in 1982 the ARPANET connections outside of the US were converted to use the new “TCP/IP” protocol. The Internet as we know it had arrived.

The creation of World Wide Web

Gopher was an information retrieval system used in the early 1990s, providing a method of delivering menus of links to files, computer resources and other menus. These menus could cross the boundaries of the current computer and use the Internet to fetch menus from other systems. It was very popular with universities looking to provide campus-wide information and large organisations looking to centralise document storage and management.

Gopher was created by the University of Minnesota. In February, 1993, they announced that it was going to charge licensing fees for the use of their reference implementation of the Gopher server. As a consequence, many organisations started to look for alternatives to Gopher.

 

The European Council for Nuclear Research (CERN) in Switzerland had such an alternative. Tim Berners-Lee had been working on a information management system, in which text could contain links and references to other works, allowing the reader to quickly jump from document to document. He had created a server for publishing this style of document (called hypertext) as well as a program for reading them, which he had called “WorldWideWeb”. This software had first been released in 1991, however, it took two events to cause an explosion in popularity and the eventual replacement of Gopher.

On the thirtieth of April in 1993 CERN released the source code of WorldWideWeb into the public domain, so anyone could use or build upon the software without charge.

Then, later in the same year, the National Center for Supercomputing Applications (NCSA) released a program that was a combined web browser and Gopher client, called Mosaic. This was originally only available on Unix machines and in source code form, but in December 1993 Mosaic provided a new version with installers for both Apple Macintosh and Microsoft Windows. Mosaic rapidly increased in popularity, and with it the Web.

The number of available web browsers increased dramatically, many created by research projects at universities and corporations, such as Telenor (a Norwegian communications company,) which created the first version of the Opera browser in 1994.

The “browser wars”

The popularisation of the web brought commercial interests. Marc Andreessen left NCSA and together with Jim Clark founded Mosaic Communications, later renamed to Netscape Communications Corporation, and started work on what was to become Netscape Navigator. Version 1.0 of the software was released in December 1994.

Spyglass Inc. (the commercial arm of NCSA) licensed their Mosaic technology to Microsoft to form the basis of Internet Explorer. Version 1.0 was released in August 1995.

A rapid escalation soon followed, with Netscape and Microsoft each trying to get a competitive edge in terms of the features they support in order to attract developers. This has since become known as the “browser wars”. Opera maintained a small but steady presence throughout this period, and tried to innovate and support web standards as well as possible in these times.

The coming of web standards

During the browser wars, Microsoft and Netscape focused on implementing new features rather than on fixing problems with the features they already supported, and adding proprietary features and creating features that were in direct competition with existing features in the other browser, but implemented in an incompatible way.

Developers at the time were forced to deal with ever increasing levels of confusion when trying to build web sites, sometimes to the extent of building two different but effectively duplicate sites for the two main browsers, and other times just choosing to support only one browser, and blocking others from using their sites. This was a terrible way of working, and the inevitable backlash from developers was not far away.

The formation of the W3C

In 1994, Tim Berners-Lee founded the World Wide Web Consortium (W3C) at the Massachusetts Institute of Technology, with support from CERN, DARPA (as ARPA had been renamed to) and the European Commission. The W3C’s vision was to standardize the protocols and technologies used to build the web such that the content would be available to as wide a population of the world as possible.

During the next few years, the W3C published several specifications (called “recommendations”) including HTML 4.0, the format for PNG images, and Cascading Style Sheets versions 1 and 2.

However, the W3C do not enforce their recommendations. Manufacturers only have to conform to the W3C documents if they wish to label their product as W3C-compliant. In practice, this is not a valuable selling point as almost all users of the web do not know, nor probably care, who the W3C are. Consequently, the “browser wars” continued unabated.

The Web Standards Project

In 1998, the browser market was dominated by Internet Explorer 4 and Netscape Navigator 4. A beta version of Internet Explorer 5 was released, and it implemented a new and proprietary dynamic HTML. This meant that professional web developers needed to know five different ways of writing JavaScript.

As a result, a group of professional web developers and designers banded together. This group called themselves the “Web Standards Project” (WaSP). The idea was that by calling the W3C documents standards rather than recommendations, they might be able to convince Microsoft and Netscape to support them.

The early method of spreading the call to action was done using a traditional advertising technique called a “roadblock”, where a company would take out an advert on all broadcast channels at the same time, so no matter how a viewer would flick between channels, they would get exactly the same message. The WaSP published an article simultaneously on various web development focused sites including builder.com, Wired online, and some popular mailing lists.

Another technique they used was to ridicule the companies that would join the W3C (and other standards bodies) but then focus more on creating new features than in getting the basics that they had signed up for correct to start with.

Lastly, the WaSP also helped, not just criticised. Seven members formed the “CSS Samurai”, who identified the top ten problems with the CSS support in Opera and Internet Explorer (Opera fixed their problems, Microsoft did not).

The rise of web standards

In 2000, Microsoft released Internet Explorer 5 Macintosh Edition. This was a very important milestone, it being the default browser installed with the Mac OS at the time, and having a reasonable level of support for the W3C recommendations too. Along with Opera’s decent level of support for CSS and HTML, it contributed to a general positive movement, where web developers and designers felt comfortable designing sites using web standards for the first time.

The WaSP persuaded Netscape to postpone the release of the 5.0 version of Netscape Navigator until it was much more compliant (this work formed the basis of what is now Firefox, a very popular browser). The WaSP also created a “Dreamweaver Task Force” to encourage Macromedia to change their popular web authoring tool to encourage and support the creation of compliant sites.

The popular web development site “A List Apart” was redesigned early in 2001 and in an article describing how and why, stated:

In six months, a year, or two years at most, all sites will be designed with these standards. […] We can watch our skills grow obsolete, or start learning standards-based techniques now.

That was a little optimistic—not all sites, even in 2008, are built with web standards. But many people listened. Older browsers decreased in market share, and two more very high profile sites redesigned using web standards: Wired magazine in 2002, and ESPN in 2003 became field leaders in supporting web standards and new techniques.

Also in 2003, Dave Shea launched a site called the “CSS Zen Garden”. This was to have more impact on web professionals than anything else, by truly illustrating that the entire design can change just by changing the style of the page; the content could remain identical.

Since then in the professional web development community web standards have become de rigeur. And in this series, we will give you an excellent grounding in these techniques so that you can develop websites just as clean, semantic, accessible and standards-compliant as the big companies’.

Summary
In this article I’ve looked at how the modern Internet was created as a result of the space race; how Tim Berners-Lee defined hypertext for a generation and how the commercial interests of two companies caused one of the most notable developer backlashes ever seen. The term “web standards” is now more widely used by web professionals that any other term applied by the W3C (infact the W3C have started to use the term on their own pages), so that is what we are going to teach you—the standards way to build web sites.
by Mark Norman Francis, dev.opera.com

Standard