Like a lot of web developers, I'm not always that disciplined when it comes to the file naming convention I use and I sometimes end up with a situation whereby I have some files that are in lowercase, some that begin with a capital, and some that are a bit of a mixture.

One web site I maintain contains about 2000 web pages and has about 20,000 hyperlinks. As you can imagine, I had one of those sinking feelings when I was told that in order to migrate the web site to a new content management system, all the file names and hyperlinks would need to be changed to lowercase.

Whenever I am presented with a problem like this, my instinct is always to write a Perl script using one or more regular expressions to solve the problem. This particular situation was no exception.

Change a string to lowercase

The following regular expression changes all the characters in a string to lowercase. The first part of the regular expression finds a hyperlink, and the second part converts the string. (Just in case this article is not displayed correctly, there should be a single backslash in front of the 'L$1').

Change a filename to lowercase

Likewise, changing a filename itself is very simple. The following two lines perform the task quite nicely:

(Again, there should be a single backslash in front of the 'L$name'.)

If you need more information on how to incorporate the above code snippets into a complete script, feel free to contact me directly.

In layman language Web 2.0 means the second generation of web development. The first generation web development is considered to be the great dot-com bubble of late 90's and the rupture of which around late 2001 triggered ubiquitous reactions that the Web was over hyped. Concept of second generation of Web development started after a media conference between O'Reilly and MediaLive International. In this brainstorming session it was realized that the web has thrown up more interesting applications and Web technology has emerged more important that ever and the word Web 2.0 was coined. Web 2.0 is a business revolution making a bent towards the web as a platform. Web 2.0 doesn't have a definite boundary and there are several things encompassing a core. Web 2.0 is visualized as principles and collection of numerous sites running on those principles at some distance from the core.

Since then Web 2.0 has remained a top level discussion for proper definition and boundary that is yet to be reached. One can simply say blogs, social bookmarking, wikis, podcasts, RSS feeds, and lightweight business over a single platform. Web is no more one way, now uploading, and downloading of information happens simultaneously, sharing and distributing contents across networks leveraging the power of "Long Tail".

Web 2.o includes numerous practices. Here are some typically implemented practices by websites:

• Well-off internet applications based on Flex or Ajax.
• This intend to allow information intended for end-users, such as contact information, calendar events, geographic coordinates, content life, social relationships etc
• Presentation is separated from content through Cascading Style Sheets (CSS).
• High-end APIs (Application programming interfaces).
• Content Syndication through RSS or Atom.
• Facility for content creation through users, also by machines from client side or server side.

Content Syndication: Syndicating partial or whole content through standard protocols such as RSS, Atom, and RDF by using XML so as to be used by the end-users for their need.

Some misconceptions on Web 2.0:

• Curvy designs (This curvy structures became widely popular at the same time, designers also started making more websites with this cool looking styles)
• Use of Ajax or Flex (Which happens to come in the same time of Web 2.0, No doubt that websites with web 2.0 architecture needs these to work well.)

Web 2.0 is not an alien to criticism and had its fair share. Here are some criticisms leveled at Web 2.0

• Web 2.0 is not a new version of World Wide Web at all. It merely uses the technologies and architectures of Web 1.0.
• Ajax is not substituting the HTML protocol; it's an additional layer over HTML.
• Blogs or social networking was features of Amazon.com since 1995 when the word called Web 2.0 dint exist. It's way more than only blogs and social networking.

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.