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.

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.

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.