Sites that require users to log in to access certain information and/or purchase products add an additional layer of potential complication to the usability process. To avoid potential visitor confusion and the possibility for errors, it is important that any login process requires little or no thought on the part of the site visitor.

Once logged in, you must be sure that visitors are able to find the information they want and expect to find. My Account pages need to provide visitors with access and ability to view and change personal information, as necessary.

Login Access

Access to any login page (or the login form itself) should be available consistently across all pages of the site. Be sure the form or link is obvious and easily differentiated from other areas of the web page.

Security

If the information behind your login contains sensitive data, you need to use the appropriate security protocols, assuring visitors that that you take their information's security seriously.

Registration

If visitors are not already registered a link to a new user registration form should be present. It's also smart to have a global link to "register" for any new visitors to the site.

Account benefits

Non registered visitors should be treated to benefits of account registration. This information should be located on the same page as the new user registration form.

Lost password

All login forms should contain an option to reclaim passwords and/or username should they have been forgotten. This information must also be passed securely.

Remember me

You can provide additional convenience (though less security) by giving visitors the option of checking a "remember me" box which will allow them to stay logged in indefinitely.

Privacy

Provide a link to your sites privacy information/policy near the login form submit button or email field. This gives your visitors confidence that you will treat their information with respect.

Status

The visitor's "logged in" status should be displayed at all times with a ready access to logout at their convenience. When additional security is necessary it's a good idea to automatically log them out after a set period of inactivity.

Change info

Once logged in, visitors should have access to change their user information, including usernames, passwords, contact info, payment details, etc.

Change confirmation

Once the visitor has submitted their information to be changed, provide a confirmation screen that shows the old and new info. This prevents errors and helps insure information remains accurate.

Financial details

Provide links to relevant financial information such as transaction history, invoices, balances, payment methods, etc. Provide printable version of this information.

Up-sell opportunities

Visitors that are logged in provide you an interested, captive audience. Consider discreetly utilizing up-sell opportunities - without being overbearing.

Subscribed services

Provide visitors access to the information/services to which they are subscribed. Also provide additional subscription options, if applicable.

Information management

Allow users to change the way they receive information, providing alternate methods such as snail mail, HTML or text based emails or to turning off communication entirely.

When visitors create an account with you they are making a commitment to you to enjoy the services or information that you provide. It's important not to let the usability process break down after visitors are committed. In fact, it's even more important to treat registered visitors respectfully and appropriately, ensuring they have access to the information they need. This develops long-term relationships and keeps them coming back.

That should be the main reason that you create a website so that it will work for you in your chosen endeavor. When you build a website it is important to understand what makes a website work.

Firstly when you go online in the research mode you type in a keyword relative to your question. Then a number of sites come up with content relative to that keyword. Then you visit a site and see if it contains the answers you seek.

The best sites are highly relevant to your search and provide content that addresses your needs. This content is laid out in a way that makes sense. Navigation is straight forward and there are few distractions. As a result you get the answers you seek and because it is presented logically in a way you can understand you relate to it and as a result you follow its recommendations.

This is exactly the way you want to build your website. Good content is king but not only that - content that is relevant and solution orientated rather that sales orientated will deliver better results. This way you become your visitor's friend and we all listen to our friends.

When people can understand and see results credibility develops. Then share a few secrets here and there and you will have a friend for life.

Get this right and you will build a website that will work for all parties concerned. This may sound a little complicated but it actually is not. We are all human beings and we have far more things in common than not. So observe how you use the internet and what your expectations are then you will understand what others expect.

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

When choosing the best content management system for your project, it is important to weigh both the technical and non-technical pros and cons. Both technical and non-technical reasons can ultimately affect the bottom line cost. Therefore, it is not recommended to simply choose a content management system based solely on technical language or feature set. In this article, we will take a look at an open source content management system called Radiant CMS.

Radiant is a Ruby on Rails based solution that works with a variety of databases. It has a few years of development and a couple noteworthy deployments. There are technical and non-technical reasons why Radiant CMS is a good choice for a content management system.

Technical Reasons to Choose Radiant CMS: It's Ruby on Rails based which can speed development by taking advantage of the convention over configuration paradigm. In addition, the Radiant code base has excellent automated coverage in unit tests. This means the code is well tested and robust. Unit test code coverage can be one aspect to measure when considering open source content management systems. In fact, we could suggest the amount of code covered by automated unit and integration tests should be considered when choosing any open source library and/or framework. It is an easy indicator to measure and compare. But, that is an entirely different conversation.

Radiant CMS also has an excellent extension system. This allows customizations required by your project to be made. When choosing a content management system, the ability to add and maintain any customizations should be an important factor. This point should be considered not only from the beginning, but how your customizations will evolve as upgrades and enhancements occur within your chosen content management system. In other words, if the core CMS is modified to provide the custom functionality, how can upgrades or patches from the core CMS developers be applied to your modified version. Radiant's extension system provides this separation of concern.

The Radius tagging system of Radiant is fantastic for adding dynamic functionality. It is nice that tags can be added directly to page content rather than some kind of comment or special character sequence in order to indicate non-static content.

Non-Technical Reasons to Choose Radiant CMS: Radiant has an elegant, intuitive administrative interface. It is not intimidating to the non-technical user. In fact, the design encourages people to embrace using the system, because they assume it is going to be easy to pick up and learn.

The lack of workflow functionality can be considered a feature in many cases. In competing CMS products, workflow can seem like an attractive feature at first, but is often hindrance to configure and work around for projects which require only a few administrators of content.

An additional, non-technical reason to choose Radiant CMS is cost. The project is open source and the community of ruby on rails developers and ruby on rails hosting providers is growing, so your cost risk of obtaining these resources is minimized.

Conclusion

From a technical perspective, the open source, Ruby on Rails based Radiant CMS makes an excellent choice. From a non-technical perspective, Radiant CMS makes an excellent choice as well. When combining both perspectives, we have had many positive project experiences and deployments using Radiant over the past year and a half.