No matter what site you build it will never be able to make money unless it gets traffic. You ask anyone online who is either new or intermediate what their biggest challenge is. The majority would say that getting traffic to their site is their number one priority.

So when building a site you will naturally want to build it in a way that will help this to happen. In order to do this you need to research extensively what way you will be able to get in front of people searching for products or information relative to your sites theme. You will need to research markets somewhat relative to your interests. For example you may be interested in travel.

Some guru's say you should not necessarily build a site around something you are interested in - instead you should build a site around a subject that will make you money. While this is understandable many people would be challenged to keep up the motivation doing something they do not like when they are starting out - because at this point there will be very little if any money coming in.

What you can do is pick a subject of general interest and then find niches within that which are profitable. This way you have the best of both worlds helping you to stay motivated and make money at the same time.

So your primary goal is to build a site that can compete with others and make you money. Develop the site in a way that the search engines will be able to understand and your visitors will enjoy. This way you will build relationships and as a result make money. To learn more on how to put all this together select any of the following links.

Looking for a way to attract more attention to your website? Offer a fresh face and new content on a regular basis and you'll find people will check back to see what's new and you'll have a tool to measure what attracts and what doesn't. Here's how to do it.

Your website homepage is your front door through which online browsers come to visit your business. Static, never-changing content is no more interesting to a returning visitor than a book they have already read. To keep your audience captivated and coming back you need to make your home on the web inviting and interesting.

Present a Dynamic Home Page

One way that you can present changing home page content is to design ten to twelve unique pages with different content and then rotate them every month. Take a couple of weeks to design different ideas and images. Create page promotions that include a message that is timeless or that has a seasonal or timely announcement such as "Holiday Specials." When you consider different features for your home page and when it should be placed you're forced to look closely at at your marketing strategy over a one year period. This will save you a lot of time since you then won't have to think about your content through the year. It also allows you to plan your offers and gather the necessary content.

A web developer can put your home pages on a rotating script or use an automatic timer. You can then rotate your home pages to highlight a new tip every month or to promote a featured product. The home page of your website is much like the front cover of a magazine. People want to see a home page that has different photos and content at least every month, preferably every week. You won't want all of the content of your website to be featured on the page as this will overwhelm your website visitors. So choose one or two features to highlight each month. The rest of your website content should be well organized within the rest of the pages of your site. When you're ready to update your home page you simply grab content from your internal pages. This way you're not having to create new content. You're just reorganizing your existing content so that it feels new to your visitors.

Don't Change Your Home Page Too Often:

Even though you want your website to be new and dynamic you also don't want to change it too often. People take comfort from their favorite websites and want them to be familiar. If you change your home page too often or too much you may create confusion or give people the feel that someone else has taken over your site. You could also compromise your positioning in search engines. So maintain some consistency.

When you make changes to graphics or content it shouldn't make a major change to the way your website looks and feels. Regular visitors should be able to find the same information that they've always found on your home page and in the same place. As a rule, the headers and navigation tools on your page shouldn't ever change without a complete redesign and announcing that to your visitors. Change content and images with other content and images while maintaining the sites original functionality. Home pages that are consistent lend a feeling of comfort to users. If your customers learn to expect consistency they'll also learn to rely on your quality customer service. If you're a small online business, gaining your customer's trust is your most important step to success.

The Benefits of a Flexible Home Page

A flexible home page lets you test your off line marketing efforts. Before you spend money on a magazine or newspaper ad you can test it out on your website. You'll be able to see how people react to the ad. It will let you determine which featured products attract the most interest. You can also determine which graphics generate the most attraction. Web analytics software (Google Analytics is great and free to use) can provide you with this type of information. It will help you obtain marketing data that is detailed and precise. You can see which graphics people have clicked on as well as what web page they were on just before they left your website.

Once you've mastered the technique of updating your home page, while at the same time keeping the core content the same, you'll be well on your way to recognizing the benefits of a flexible home page.

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.