Attention all business owners! Do you know the answer to this question: Who gets to keep the website after you divorce your webmaster?

Just like in a marriage, it all depends on the pre-nuptial agreement (contract). Do you have one?

My personal disclaimer: Some of this information may be about legal issues; however this article is not intended as a substitute for legal advice. I am not an attorney nor do I play one on webTV therefore you should consult with an attorney familiar with the laws concerning internet and intellectual property.

Ok, now on with the story, the short version. . .

Here's the situation, for whatever reason the client decided not to pay their annual bill for web hosting services. Even though there were several attempts to reach the client the bill went unpaid for more than 90 days. As a result, the hosting was cancelled and the site was removed from the server.

Several months later the client sent this exact message: "you have my website and I need you to let me know how to get it back, like I said before I paid you money to build it so....? that money had nothing to do with hosting or anything".

Just because you paid for the development of your website does not mean you own it. There are Intellectual Property laws designed to protect the creator and to encourage the creator to create. If you hired a company they own the software development and website design produced by its employees. If you hired an independent contractor you must obtain a written "assignment" of the copyright in the commissioned work from them.

Most business owners unknowingly give their webmaster complete control over their business website. Even if you don't have a pre-nuptial agreement (contract) or own your website you can still maintain some control. While you and your webmaster are honeymooning be sure you can document the answer to these questions:

1. What software was used to develop the website?

• Exact name
• Version
• Software website

2. How to access the code?

3. Where is the code located on the server?

4. How to change the content?

• Graphics
• Text

5. How to create a weekly back up?

6. How to grant access to additional users?

7. How to obtain the master copies of your website design?

As a business owner, how many people realize their webmaster is like their spouse? Voluntarily joined for life (or until divorce), not many! Just like in marriage a prenuptial agreement (contract) is a practical solution to dealing with the risks and problematic topic of who gets to keep the website after your divorce.

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.

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.