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.

The very fact that you are reading this article indicates that you have something in mind that you wish to achieve. Your goal more than likely right now is to connect the dots. When it comes to inventing anything it begins with an idea and then you seek out ways to make it happen.

I do not know exactly what your ideas are but whatever they are you need to put them on paper. This will help you to stay focused. So for example let's say you love dogs. So you have decided you want to build a site all about dogs however right now you do not know how to go about it.

The first place I recommend you start is with article directories. Punch in the keyword dogs and see what people are writing about. Then pick an article and see how many page views it gets.

Then look for articles in this category that get the most page views. This will tell you that a lot of people are reading about these topics and as a result are seeking information which is what the internet is all about.

Once you find a topic that you like that generates a lot of page views then head over to google and type in the keyword associated with this content and along with the keyword type forum. On the forums look for relative topics that receive a lot of page views and see what people are looking for.

Then take the keywords and go to wordtracker and use their free trial. What you are looking for are keywords that have a high KEI that is at least above ten. Once you find the right combination you now have the foundation upon which to build your site.

Next up get a domain and you can if you want include the keyword in it but you do not have to. Then get a hosting company that is reputable that provides good customer support.

Finally you need a html editor so that you can structure the pages properly so that the search engines can understand the content. Once all this is in place you will now be ready to build your site. You will also have lots of information to help you write articles and get traffic to your site immediately.

To learn how to build a site that works select any of the following links.

Reusing pieces of HTML code is a common way of making web sites (or web applications) more consistent, reliable, and more manageable. Even a small web site consisting of perhaps 20 or 30 web pages can benefit from reusing code for header and footer sections, for example. If the same header or footer is used across all the pages on the site, it makes sense to put the header and footer code in separate files, and then call those files to insert their contents where required.

PHP offers two statements that can be used for inserted the contents of one file inside another: include() and require(). These two statements are virtually identical, with the only real difference being that if require() fails, it gives a fatal error, whereas if include() fails it just gives a warning. For this reason I tend to use the include() statement as it just seems slightly more friendly.

So, to include the contents of a file called header.inc inside a web page called index.php, you would just need to insert the following line of code (wrapped in PHP opening and closing tags) inside index.php.

Include 'header.inc';

As PHP takes no notice of the extension used for the included file, you can use whatever extension you want to. Be careful though, if you put passwords inside an include file with a .inc extension, they will be visible. You can get around this by putting include files that contain sensitive information outside the document tree to prevent people from browsing to them.

In Part 2 we'll look at the use of functions when developing web sites and applications.