When it comes to building websites you need to understand what you fundamentally wish to achieve. This should be front and center. This way you stay focused on your overall goal which will help you stay on track when it comes to research.

One thing a lot of people fail to remember when building a site is that you will need to effectively communicate with people. Sure you will be doing a lot of keyword research but behind those keywords are people who need something and you need to communicate with them.

The mechanics of the site will be based upon the keywords you choose. This will determine the navigation and overall theme of your site. Getting this right is really important. This will also help you to achieve good rankings on the search engines.

For effective keyword research you will need to visit multiple sites to determine how best you can position your new site. Everyone will tell you that you need low competition keywords with high volume searches - while this is sound advice it can be tuff to achieve but that does not mean that you should not do it.

Where I change the game a little is by starting with the article directories and looking for keywords with articles that achieve high number of page views, this way I know I can write an article and get immediate quality traffic without having to wait for the search engines.

This can bring you advertising revenue and sales. When it comes to building the site itself there are lots of site building software out there. The one I had the most success with starting out helped me to get into the search engines and took care of hosting and good link development along with a solid site structure.

To learn how you can put this work for you select any of the following links.

Things which exist on one's personal computer are referred to as "client side", and on the web host as "server side". The average internet user might have first heard "client" in the context of applications installed on the personal computer, such as "email client". Those mail systems which can be used from anywhere are "web mail", and exist on the server side.

In practical terms, all your office suite programs, media players, programs to edit images, most games, and so forth, are probably client side, although "utility" type functions are evolving on the server side. For example, users can now share data on server side spreadsheets and word processors.

Most browser function is defined on the client side, perhaps with some JavaScript add-ons for interaction, calendars, multi-level menus, animated graphics, et cetera.

Business enterprise level content management, databases, store systems, and much more are on the server side. Server side programming can range from simple CGI scripts ("Common Gateway Interface") written in a variety of languages, such as Perl. Large databases can be built in the popular open-source MySQL, and accessed through interfaces programmed in PHP.

First embodiments of such CGI functions started a new copy of the executing module for each command request. To avoid server shutdown from excessive workload, host programmers have evolved better ways, but these need not concern us ordinary mortals.

Fortunately for this author, a web site builder does not need to be an expert in all those server side tools in order to use them. Most hosting companies now offer access to pre-installed modules. Persons wanting better features can purchase modules from third parties to upload and install, such as shopping carts, which are backed by support staff, user, or similar.

If the site builder lacks a very fast connection to the server, s/he can install client side copies of operating systems for SQL, PHP, other... to emulate behavior on the host. Sometimes the emulation is less than perfect, such as with different release generations, so adjustments may be needed after upload.

Why would anyone bother to do this? One reason is that PHP can take over parts of HTML coding, such as with "include files" which represent often used sections of header, footer, body, or serve more robustly than JavaScript for interactivity and utility functions.

If the connection is fast, however, present day "shared hosting" and "virtual private/dedicated servers" make it very difficult for one domain owner to break the system for other users. And only privileged employees have access to the power switch. VPS allows power users to get more behind the scenes than can the SH customer.

Caveat: Whether your HTML writing is done directly on host account or on personal computer for upload, keep an off-site copy against the day your hosting company drops or back levels your content. It will happen.

What ever the approach a person uses for working on the internet, all these elements are examples of "distributed processing", a concept which some large mainframe computer manufacturers had hoped would never be realized. Now that the small guys and gals have forced the issue, by using ever more powerful personal computers in place of dumb terminals, the big dogs have learned to love and profit from it.

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.