Normally, if you want a professionally designed, custom-built website for your new virtual assistant business, you should be prepared to spend at least a few hundred dollars.

But, all that can change if you know where to find the best deals and the best designs for the lowest price.

First, it costs more to have a brick-and-mortar company design a website for you. Have you seen those newspaper ads that offer a 5-page website for $500? These are probably companies with physical locations. They have to charge more simply to pay for their overhead: office rent, designers' wages, advertising costs and so on.

Therefore, it would be wise to use a virtual assistant (VA) instead! As you already know, VAs often work from home so they do not have high operating costs like a big company does. On the other hand, a VA will be able to design images with quality similar to (or better than!) those of designers from big companies.

However, choose your VA with care. The best way to find the right VA for your project would be to go to visit the website of a VA association. There you can post your RFP (request for proposal) and have hundreds of talented VAs bid on your project, so you will get the best deal. You will also be able to choose your designer based on her experience, past transactions and client testimonials, so your value for money is secured.

Another route you can take is to purchase the Virtual Business Startup System, created by Tawnya Sutherland. It comes with several beautiful, easy to use templates, perfectly suited for a new VA. The templates are easy to edit wth the help of WYSIWYG (what you see is what you get) programs such as Microsoft Frontpage, Macromedia Dreamweaver and so on.

Some working knowledge of J2EE or JSF is assumed for this article.

Like some of you I've been frustrated with this technology known as JSF or Java Server Faces. There are several different flavors out there that are built on the shoulders of JSF. For instance Oracle's ADF (Application Development Framework). Oracle ADF Faces Components is a set of over a 100 JSF components that let you build a richer user interface for your Java EE applications. Oracle ADF Faces also includes many of the framework features most needed by JSF developers today.

That is great, and in many ways it will make life easier to develop in a JSF environment. Some items you will find available in these "add on" packages have a real benefit. For instance, as of the date of this article, I was very surprised that a File Upload is a feature still not implemented in JSF in respect to using natural jsf tags. There are ways to accomplish this task in JSF but they are not native JSF approaches. The process is a "no brainer" in just about every other framework available today, including asp.net.

Another simple task (I thought) was having a data table present the results of a query in an editable format. Possibly to update a user record or shopping cart. After working in other technologies it was very efficient to return a result set to a data table object and let that object take care of some of the trivial behaviors and characteristics of the table itself. When I started exploring JSF I was frequently and at every turn becoming more and more frustrated in trying to duplicate some of the most basic of processes similar to managing records through data tables.

There are not a whole lot of resources out there yet on JSF although it is growing steadily, and I found that all too often the resources that I was finding on the internet either didn't apply to the more simple tasks or the information was just completely wrong. One example of that was that it was stated in one article I read that you cannot use command buttons inside of a JSF data table. The recommendation was to use JSF hyperlinks instead when trying to perform an action from a data table due to a bug in the framework that prevented command button actions to fire if the button resided inside of a data table.

At first I thought "you've got to be kidding me"! Then I remembered that I've been finding a fair amount of "bogus" information in regards to JSF development so I decided to do further research and discovered that information to be less than accurate as well.

I simply had to find a way to populate a data table through a result set and get a command button to fire an action and pass all of the data in the data table to the backing bean to update the record. Multiple command buttons would exist as well as hidden fields pertaining to id numbers and so forth. Pretty basic stuff and we've all done it before with relative ease.

It turned out that the solution was in fact a simple one. "Binding". You've heard about it and read about it. But this approach was something a little different as far as I could find.

Many of the blogs and articles that I read dealt with passing the values as parameters and following the steps to define the parameters in faces.config files etc., then retrieving the parameters in a backing bean. Processing the passed data required another set of procedures to utilize mapping to each of the field parameters passed and then processing could begin.

That seemed like a whole heck of a lot to me just to retrieve form data. Then it occurred to me that I should be able to "bind" a text field component on a page to a backing bean. Once it is bound then all I have to do is extract the data. And that's all there is to it. My query returned results and pre-populated a data table including text fields with the values of the query pre-populated in the text fields.

Each one of those text fields was bound to a "HtmlInputText" type in my backing bean. It was not a String type like other approaches define. Doing that does require you to map parameters and populate that String variable through your set methods once the form is submitted.

What I found is that if I bind my text field to a property of text field type that it solved my problem of passing values from a data table, and I didn't have to define parameter fields anywhere in any xml file. Now that I had that figured that out I needed to figure out how to get the value of that property that I've bound my form field to, well why not getValue()?

I personally hadn't seen any examples online or in books for retrieving the value from a form binding it to the type of form element it was and simply use the getValue() to pull out the value of the object. Used like this getParameterFromForm().getValue().

Let me clarify that I am NOT saying that trying this approach isn't documented anywhere, I find it hard to believe that I've had some stroke of genius that no one has had before in the world of java, especially since I'm coming from .NET and ColdFusion.

After doing that I no longer had any problems passing form data to my backing bean. I was able to dynamically populate data tables with any number of records including any number of command buttons within that data table and I didn't have to concern myself with remembering to define parameters in any other areas of the application.

So put simply you can bind your form fields to properties of the same type in your backing bean, and then extract the value of that object using getValue() if you prefer over utilizing parameter string mapping and similar approaches for processing form data. I found it to be easier and less time consuming which has costs associated to it as well.

What do you think is the most important aspect of a website? Let me put the question the other way around. When you go online and visit websites what do you look for? The first thing you want is information. This helps us to make decisions.

Before you buy a car for example you want to know what the safety ratings are and how many miles per gallon it gets. Then you may want to compare it to other cars in that category. All this information is provided through content.

Good content on a site helps you to make decisions and when you experience this you feel you are getting results. As a consequence of this credibility develops and you will use this website as a reference guide which means you may visit it again.

This makes sense right? It's funny because often the secrets to success lie right in front of our eyes. Many times we tend to look elsewhere rather than our own actions for answers. Good content will not only benefit your site visitors but it will also help you climb the ranks in the search engines.

So when you create a website you want to build it in a way that it can provide good content. Good content is brought about by good research. Research is key as this will help you to put a solid foundation in place.

Good content will provide good advertising opportunities and your recommendations will have credibility which will lead to sales - either of your own product or somebody else's.

While all this may seem a little over your head at this point it will all become clear as you work your way through it. Start with a subject you like and start researching niches relative to it. Then you will be focused and in a far better position to build a money making website.

To learn how to put all this together select any of the following links.