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.

Let's begin with a little history. Many years ago, when the web was up and coming and you needed to be on it, I paid someone to build a site for me. Afterwards, I could say, "Yeah, I have a site, go to -" and then I would name my site a feel a hit of pride. I'd also get satisfaction when my webmaster (if you could call him that; I don't know that I would in retrospect, but that's another story) occasionally forwarded me an email of an interested visitor. My satisfaction was short-lived, as you might imagine. I soon began to understand the power of the web and found the sad reality that my "webmaster" was getting all my emails from my website visitors to be annoying. I had him change this so that the emails came to me. He charged me a one-time fee for getting him to do this.

Okay, so these days it is not quite that bad, is it? Your webmaster or whoever is doing the "web thing" for you isn't charging you for every little service? Excuse me. I'll reserve my rant for another article, or possibly a blog entry.

So anyway, I fired my webmaster. I built my own webpage. I did this - of all things - with Microsoft Publisher. Yeah, well, it worked - in that I was able to build a site and, with some effort, get it on the web. I won't go into why you shouldn't try this, kids, at home. I was at home when I tried it, sure. But I don't suggest building a site with Publisher. It can be done, but don't do it.

One thing that happens - talk about annoying: The site crams all against the left side of the page. There's nothing you can do to change that. You might as well type out onto the web page "Look, Ma, I can create a website using Publisher." Don't do it.

Well, I knew at the time I shouldn't be messing around with Publisher. It's great for putting together a book or something for print. It's not good for websites. I had just been so excited because I had created a downloadable book for lulu.com. Publisher was great for laying out a book. I had so much momentum...

I put the Publisher site up, and thought I had done a pretty good job, considering that everything was crammed up to the left of the screen. I had yet to become a blogger, and I had yet to realize the importance of tagging and so on. All that important "extra" stuff. I'm joking. Writing tags is not extra. It's essential. So is the blog - on the website.

Then I bought FrontPage and a book and... That's all she wrote. I learned FrontPage and I haven't tried anything else out since. Why not? So far I don't need to use the fantastic Dreamweaver that everyone talks about. Oh, I can't do Flash on FrontPage? Uh - yes you can. Easily.

I continue to believe that content is all-important. Not bells. Not whistles. Content. I don't care what kind of a site you are putting up. Well, okay, I wouldn't necessarily use FrontPage for every circumstance. But for you and me, the individual or small company that wants to be up and shining on the web, FrontPage is the clear answer. At least it was for me. As I say, I haven't looked back since.

One needn't learn the bells and whistles. One certainly needn't incorporate dhtml or whatever that code is that will make letters pop and fly about. Old browsers can't see it, and new browsers - mine, at least - don't want to see it.

I have affiliated with companies. That is, I've tried to turn a dollar by putting them up on my site, a link or banner or what have you. Let me say that what I don't like are the banners that flicker and blink and all that junk. If I want the Las Vegas experience, I'll go there.

Just give me content. FrontPage can handle that and handle it well. You want to be able to upload Flash, for sure. FrontPage can do it. You want to be able to get as much information on your website with as few bytes as possible. FrontPage can do this as well as any program. So, I'm happy. Are you happy - yet?

Dear Reader,

Site Rubix is a new website building tool recently released (Oct 2007) from Kyle and Carson at Wealthy Affiliate.com.

I have had a chance to use this website building tool, and I have to say it does do 'what it says on the tin'. It is very easy to use. You can choose a website style from an array of templates, drag and drop, add images, video, text, and actually publish your own site to your own domain with the click of a button. Because it is free along with Wealthy Affiliate membership you also receive free hosting.

The only thing you have to do independently is purchase your own domain, which is an easy thing to do. You can do this by visiting any number of websites which register domains, for example 1and1.com or GoDaddy.com.

The instructions for using Site Rubix are very clear, which is what you would expect from the Wealthy Affiliate team, although you will find it so user friendly you almost don't need to refer to the instructions except perhaps for the actual publishing step. This is when you actually make you site live and online, and again this step is not a problem if you follow the simple step by step instructions.

I would recommend Site Rubix as a website building tool, particularly to someone who is building their first site. There are no headaches involved, its quick to use, good functionality, you don't need to know http. All in all, its a pretty good system all-round.