There are a lot of reasons you might want to start a website. It is a great way to communicate with friends & family, and it is a great way to meet new people online and create conversations on the internet. Whether you have an idea or belief you want to promote, or a product you would like to sell, a personal or business website can be the solution to your marketing and communication goals. These days, a lack of technical knowledge doesn't have to be a barrier to getting started.

The good news is you don't need a degree in programming to start a new website. You don't even need to know a single line of code for that matter! If you can install software packages through a web-browser interface, you can set up a Content Management System (CMS) that will allow you to design, create, and manage any number of pages, articles, and stories. Some web hosts even have utilities like Fantastico that will automatically install a variety of Content Management Systems from blogs, to forums, to picture galleries or e-commerce websites.

Content Management Systems not only give websites more interactivity and functionality, they also allow people with few technical skills to get up and running with an online presence. The most popular ones like WordPress, Simple Machine Forums, phpBB, and Joomla are all free to use with varying regulations on how you can modify or transfer use of the software. Each of the programs also has discussion communities built around them where new and experienced users share advice & knowledge with the most common errors and user requests. If a problem pops up, there is a good chance that someone has already posted a step-by-step solution to it somewhere on the web.

As easy as it is to create and initially customize a new website, there is also no limit in how far you can take it. As you install easy to use CMS packages, some of the vocabulary will become a little more familiar and you'll naturally find yourself a little more comfortable with the technical aspects of your new hobby. So long as you keep regular back ups, you can confidently learn new skills by trial and error.

Some people say that using a splash page as your home page is a bad idea. And that's true. You shouldn't use a splash page as your home page for search engine optimization purposes. Search engines love content, and having a splash page as your home page defeats your purpose of ranking well in the search engines, if that is one of your goals.

A splash page actually is a good idea - if you don't use it as your home page.

For example, a splash page on a traffic exchange is an excellent strategy and it's actually one of the best ways to eke out results from traffic exchanges.

You can set your splash page as an extension. For example, yourdomain.com/splash.html. Then use that for appropriate marketing channels. A splash page works well to get a visitor interested in a site because it's consistent two-step marketing. Get someone to do something, and he is likely to follow-up on whatever you tell him to do next!

So go and create a simple splash page now and use it for marketing channels like traffic exchanges, classified ads, pay per click ads etc. Splash pages are uncannily effective when the situation calls for something less cluttered and more attention grabbing. For the traffic sources mentioned above, splash pages definitely fit the mold.

Hire a graphic designer to create a snazzy graphic for you to use on your splash page. After all, the goal of your page is to capture immediate attention! You can even create a simple Flash movie or even include a video there.

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.