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.

If you have decided to use website templates to create your ideal website you have taken a step in the right direction. This is especially so if you don't want to spend thousands of dollars on custom templates and do not have the ability to create them on your own. Many people think that once they have the templates they are ready to roll, and you are in a certain sense. But, there are some things that you should do to make sure that you preserve the integrity of the template so you can use it again and again if needed.

After You Purchase Your Flash Templates

There are many sources for web templates and whether you buy them to install on your computer or you download them the very first thing that you should do is save them in their original format. So many people open the template and they are ready to jump right in and start designing their website right away that they don't take a moment to save the template the way it is.

The reason that you want to save the template "as is" is because many who are new to working with templates end up hitting enter one too many times or they end up changing the font or changing the format of the page and they cannot get it back. It does take some practice to work with templates without disturbing their original integrity and if you know that you have the original template saved you don't have to stress out every time you distort the template somehow.

The great thing is that a lot of the templates out there come with some basic directions. If this is the first time you will be using templates you should take a look at the instructions and see what you can learn from them. Many times simply glancing at the instructions before you dive right in will allow you to decipher between the different layers of the template so you are able to add text and images with ease.

Slow Down and Then Begin

Many people get their templates and they want to rush into building their website. Whether this is your first time using templates or building a website or the 10th you need to take a deep breath and then begin. If you rush into building your website you won't give it the attention that it needs and the quality will therefore be less than you had always imagined that it would be. If you slow down you will be able to give attention to the small details that really make a webpage functional and aesthetically pleasing. It doesn't matter what sort of webpage you are building, slowing down and preserving the integrity of the template is important so you can return to it again and again or avoid the frustration of trying to fix what has been distorted through the trial and error of using a website template in a rush.

The thing about computer languages is that there is some weird heaviness on the actual work involved. People are scared of by codes and although they see the power, they just can't seem to get going because they have no idea where to start.

That is where training comes in. And of course, fun training. You need to be taken by hand and shown exactly what you need to do, where you need to do it, and when you need to take the right action.

The funny thing about CSS is that it allows you to create your website in the fraction of the time when you would do it using tables. It's hard to believe, but still after all these years of promotion for CSS people (and companies!) still heavily rely on tables for layout. They have no idea that they are simply wasting time on old techniques that will be useless in a matter of time.

So where do you need to pay attention on when you are looking for a CSS Guide?

1. The Teacher

The number one thing you need to be sure of is that your teacher knows where he or she is talking about. Why is he or she teaching about Cascading Stylesheet, because they need to from their boss? Because they think they can teach, no matter the subject?

Think of that, how many teachers are only "teaching" stuff, and never practice it their own? Ask yourself "why" are you teaching you me this. Are you the best in the field? Where did you get your knowledge from?

2. Teaching Style

So the teacher may be a great person, has all the required skills, has a passion for the subject and knows about everything of it. But can your teacher deliver? Does he or she KNOW how to explain things? How to take you by hand and show you step-by-step how things work?

Is it fun to follow along with the teacher? CSS is one of those topics that can become boring easily when it's only discussed in a technical way. Make sure you know what you can expect!

An even more important thing is cutting right to the case. You don't want to end up with all kind of knowledge that you will never use in practice. It simply isn't useful to learn every possible css style there is when you just get started. And this brings us to the third point you need to pay attention on when you are looking for a css guide.

3. Teaching / learning speed

Can you keep up with the course? Does your teacher decide the speed, or do you? Of course a great way to follow a course is one that allows you to define your own speed. Home study courses and guides are wonderful for that.

4. Delivery

How is your guide delivered? Are you somebody that likes to read, follow along with a training video or both? Decide what you like, training videos are great, because they allow you to follow along in a real life situation. This means hands on practice, which is exactly what you need if you want to become good in CSS.

5. Contents

Last but not least, content. What is discussed in the guide? What is marked as important? Do you get a total reference, or do you know you don't need that, that the real thing you need is a hands on course with day-to-day subjects? Decide what you want to know, just the basics, how to create full layouts, or just how to create a menu using 100% CSS.

It's up to you now, decide what you need, you know how important the 5 above points are, and where you need to pay attention on. And one last tip, make sure you get some preview videos or sample chapter before following any course, it can save you a lot of time and money at the same time.

Hilco van der Meer
CSS Expert