Dear Reader,

Site Rubix is a new website building tool recently released (Oct 2007) from Kyle and Carson at Wealthy Affiliate.com.

I have had a chance to use this website building tool, and I have to say it does do 'what it says on the tin'. It is very easy to use. You can choose a website style from an array of templates, drag and drop, add images, video, text, and actually publish your own site to your own domain with the click of a button. Because it is free along with Wealthy Affiliate membership you also receive free hosting.

The only thing you have to do independently is purchase your own domain, which is an easy thing to do. You can do this by visiting any number of websites which register domains, for example 1and1.com or GoDaddy.com.

The instructions for using Site Rubix are very clear, which is what you would expect from the Wealthy Affiliate team, although you will find it so user friendly you almost don't need to refer to the instructions except perhaps for the actual publishing step. This is when you actually make you site live and online, and again this step is not a problem if you follow the simple step by step instructions.

I would recommend Site Rubix as a website building tool, particularly to someone who is building their first site. There are no headaches involved, its quick to use, good functionality, you don't need to know http. All in all, its a pretty good system all-round.

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.

Not long ago, a friend of mine sent me an email asking for my opinion on whether a site he was developing should be done using Wordpress, LAMP, or ASP.NET. I've used all of those, but have always been so focused on the details and learning them that I never really thought about the great question of "What technology should be used for a given site?". That is such a good question that I decided to put my thoughts on paper and help provide some education to others.

Some people don't have the skills and ability to actually be able to choose the most appropriate technology. They know one thing and that is going to have to be made to work in all cases. That's not necessarily bad, but it's nice to be able to switch between technologies based on the type of site. The important thing to realize in web site development is that one technology does not fit all.

Wordpress

I have several web sites currently running Wordpress. I originally thought of Wordpress as just a blogging platform. While that is certainly its main use and what it is optimized for, you can definitely use it to create a more "traditional" looking web site. It is very configurable and there are tons of custom plug-ins available that can allow you to add RSS feeds, SEO tags, voting, etc. Since Wordpress is developed using PHP and MySQL, it is also possible to create your own plugins and customize your site template. Oh, and that's the other incredibly awesome thing about Wordpress -- the templates! There are literally thousands of free Wordpress templates available for download. If you can't find one that fits the theme of your site than you aren't looking hard enough.

Another nice thing about Wordpress is that you can easily find web hosting providers that support Wordpress. In most cases, you can click an install link and have Wordpress properly installed on your site in a few seconds. Then you go to the Wordpress admin console and configure your site. It is all very easy. You can upload multiple templates and easily switch between them. It is also easy to make minor changes to the templates (like changing tag lines, colors, etc.).

The other benefit of Wordpress is that it is a blogging platform and the search engines love blogs. You can configure your Wordpress install to automatically ping one or more blogging services whenever you add a new post or page. That way they know your site has changed and they should come index your site again. If you want your site to be found then using Wordpress as the underlying engine is a good option.

LAMP

In case you don't know, LAMP stands for Linux-Apache-MySQL-PHP, which is a very common and powerful set of technology components used for building web sites (and did I mention completely Open Source and free!). If you want complete control over your web site, then LAMP is a good option. There are plenty of examples, free scripts, etc. available on the web site to help you get started. There are also plenty of free editors and tools to help you along. The downside of LAMP is that it is hard for you to create your own development "environment". Since most of us run some flavor of Windows as our desktop operating system, we would need to use something like VMWare or Virtual PC to create a virtual machine running Linux. The next challenge is getting all of the components properly installed. While the installers for the LAMP components have definitely improved, they still don't compare to the ease of installing a Windows-based application. The next challenge with LAMP is debugging. It would be nice if we all wrote perfect code, but the reality is you need the ability to debug. There are PHP debuggers available. A good one is going to cost you some money though.

One of the best things about LAMP is that there are TONS of web hosting providers out there for you to pick from. The reason is quite simple -- LAMP is completely open source, so it there is very little cost for the hosting company to bear. That means more margin for them!

ASP.NET

Microsoft's contribution to web site development is ASP.NET. You can use any .NET language (C#, VB.NET, Python.NET, etc.) to develop an ASP.NET based site. In my opinion, the best thing about ASP.NET is the fact you can use Microsoft Visual Studio for you development tool. Visual Studio is the best tool out there. Yes, it costs money, but you definitely get what you pay for. The other nice thing about ASP.NET is that you can easily develop on your Windows-based desktop or laptop.

It is harder to find a good ASP.NET hosting provider. Believe me, I've looked! And I've used several different ones. The ASP.NET providers lag behind the LAMP providers in terms of what they offer. You also need to be careful and really understand what the provider means by things like "host unlimited # of domains". In many cases they just mean you can have an unlimited # of domains point to your single web site. That probably isn't what you want.

I mentioned the use of Visual Studio before. That tool is awesome and makes development SOOOO much easier. I did quite a bit of development using LAMP and got some sites up and running. I used Eclipse with a PHP plug-in and it worked pretty good. I didn't have Apache running or Linux, so couldn't really debug but I still managed. When it came time to create a more advanced web site, however, I quickly decided to switch over to ASP.NET and use Visual Studio. Debugging was a snap and the coding was made much easier thanks to Intellisense and Visual Studio's ability to "import" web services and make them easier for me to call from my code.

Making the Right Choice

Each of the technology options has pros and cons. If you want to get a site up quickly and it will be displaying basic information (text, images, video) then Wordpress is a great option. If you want a more advanced web site but don't want to spend much money on development tools, then LAMP is the best choice. Finally, if you already have Visual Studio or know .NET programming, then ASP.NET is a good option. If you're really lucky and can know all three then you can use the right tool for the job no matter what.