In layman language Web 2.0 means the second generation of web development. The first generation web development is considered to be the great dot-com bubble of late 90's and the rupture of which around late 2001 triggered ubiquitous reactions that the Web was over hyped. Concept of second generation of Web development started after a media conference between O'Reilly and MediaLive International. In this brainstorming session it was realized that the web has thrown up more interesting applications and Web technology has emerged more important that ever and the word Web 2.0 was coined. Web 2.0 is a business revolution making a bent towards the web as a platform. Web 2.0 doesn't have a definite boundary and there are several things encompassing a core. Web 2.0 is visualized as principles and collection of numerous sites running on those principles at some distance from the core.

Since then Web 2.0 has remained a top level discussion for proper definition and boundary that is yet to be reached. One can simply say blogs, social bookmarking, wikis, podcasts, RSS feeds, and lightweight business over a single platform. Web is no more one way, now uploading, and downloading of information happens simultaneously, sharing and distributing contents across networks leveraging the power of "Long Tail".

Web 2.o includes numerous practices. Here are some typically implemented practices by websites:

• Well-off internet applications based on Flex or Ajax.
• This intend to allow information intended for end-users, such as contact information, calendar events, geographic coordinates, content life, social relationships etc
• Presentation is separated from content through Cascading Style Sheets (CSS).
• High-end APIs (Application programming interfaces).
• Content Syndication through RSS or Atom.
• Facility for content creation through users, also by machines from client side or server side.

Content Syndication: Syndicating partial or whole content through standard protocols such as RSS, Atom, and RDF by using XML so as to be used by the end-users for their need.

Some misconceptions on Web 2.0:

• Curvy designs (This curvy structures became widely popular at the same time, designers also started making more websites with this cool looking styles)
• Use of Ajax or Flex (Which happens to come in the same time of Web 2.0, No doubt that websites with web 2.0 architecture needs these to work well.)

Web 2.0 is not an alien to criticism and had its fair share. Here are some criticisms leveled at Web 2.0

• Web 2.0 is not a new version of World Wide Web at all. It merely uses the technologies and architectures of Web 1.0.
• Ajax is not substituting the HTML protocol; it's an additional layer over HTML.
• Blogs or social networking was features of Amazon.com since 1995 when the word called Web 2.0 dint exist. It's way more than only blogs and social networking.

'Fully integrated' is a term used to describes websites that are progressive enough to include virtually every form of online media in their web presence.

If you look at sites like Yahoo, Forbes and virtually any of the major television network sites you can gain some idea of what I am taking about.

These sites contain either news of blog information. They also contain original video streaming sources and audio streams including podcasts. These sites tend to subscribe to the idea that the web user wants it all and should be able to find it all when they visit the business site.

A fully integrated site will often use flash or other animated or moving text. The interesting dynamic is that the best of these sites understand navigation and ease of use remains a critical concern for guests.

Forbes, for example is highly adept at slideshow type presentations on a multitude of topics. It could be top selling cars, entertainers, vacation hot spots, etc. These slideshows are optimized for search engines and are easy to breeze through.

It seems as if a site like this has the potential to garner some of the same consumers of media that have been courted mostly by network television or traditional newsprint.

Most fully integrated sites did not start off that way. In most cases they worked through issues they could easily address and then added features as their knowledge and confidence grew in relation to the their site development skills.

That's something I have always suggested. Do the best you can at developing a site with the most comprehensive development techniques at your disposal. That doesn't mean you have to have a fully integrated site in order to conduct business, but it does mean that you do not simply wipe your brow, release a sigh and suggest to yourself that your work is finished.

The truth is there are more skills in online web development that are being released than ever before. More programs are working with each other allowing a new robust platform for online use. The role of online web development is an ever changing - ever growing function in relation to how you manage your site and in the use of the most effective marketing tools available.

Many sites will develop an internal compass that provides the date they want to upgrade the website to include new functions. In essence they treat their website like software developers treat upgrades. Some will even go so far as to indicate their website has gone from version 1.0 to version 1.1 or 1.5. The idea is to challenge their own thinking in relation to developing a website even after the website has been launched.

This has the potential of keeping visitors interested in finding out what improvements you will come up with next.

Perhaps the greatest development rule of thumb is that you should always strive to be more integrated by attempting to meet the real and perceived expectations of your site visitors. This mentality will always give you a new goal line in your race for the perfect business.

Most web development projects include one or more of the following elements...

• Database design and creation
• Server-side computer programming
• Client-side computer programming
• Web page design

Each of these elements has to work in its own right, and in cooperation with the other elements. The more complex the project, the harder it is to bring it all together and make it work correctly.

How to keep the cost down

Here's how you can make sure your web development costs don't run over budget...

1. Insist every aspect of the development is described in an Agreement document, and make sure both you and the developer sign it
2. Don't make changes after work has started

The key to achieving the second of these two items lies with the first. You should insist that an Agreement document be created, and sit in on the process.

You need both end-users and developers in the same room, working through each aspect of the development. The end result must be a document that fully describes the development, is clear (unambiguous), and easily understood by both users and programmers.

Every minute you invest creating this document greatly increases your chance of bringing the project in on budget.

Why it's worth it

Many of the problems that usually cause headaches during a complex development could have been discovered in advance, if an Agreement document had been created. When users and programmers get together and discuss their respective needs thoroughly, the resulting development is far more likely to go smoothly.

This kind of interaction forces both users and programmers to think through what's actually required to make the system work. The ongoing interaction reduces the risk that person A assumes person B knows what they're talking about.

Users are committing to a specific set of functions for an agreed price. The developer is committing to develop those functions for an agreed price. This means both users and developers have a self-interest in being thorough.

Should a user change his/her mind about something after the Agreement document is signed, the cost of development must be renegotiated. This punishes the user for failing to think things through.

Should the developer discover he/she hasn't fully understood what's required to complete some aspect of the project, he/she can't ask for more money. This punishes the developer for failing to break down each stage of the development and understand what's involved in completing it.

Assuming you do your part, you won't need to make changes after the work has started. As a result, you'll bring the project in on budget even if the developer hasn't done his/her job properly.