The content management system you choose can really make a huge difference in how much time you (or your clients) spend keeping a site updated and maintained. There's a huge variety out there-some estimates put the number at around 1700 different options. Some are great...some, not so much.

Among the suggestions are things like:

• A CMS needs to work intuitively.
• The backend needs to be logical and well-organized.
• The right CMS shouldn't have a ton of extra functionality you'll never use.
• The right CMS should be easy for non-geeks to use.
• The pages it creates should be fast-loading and have simple code.

They also mention a few options available that might be a good fit for you and your organization: WordPress, SilverStripe, Joomla! and a few more.

It was over a year ago that I wrote the article that compares CodeIgniter and Kohana. Since then both CodeIgniter and Kohana have seen major progress with the release of CodeIgniter 1.7.0 and Kohana 2.3. [...] Let's see how they compare with each other.

He judges on a list of criteria including licensing, supported databases, community, documentation and modularity. Ratings are gives for each framework (like "Excellent" or "Good") on each item with over twenty aspects considered.

• PHP 4 or 5? - if you haven't made the switch to PHP5, there's no better time
• Linux/Apache - Windows is largely an ASP.NET platform
• Access to outside the document root - it can be very useful for templates, config files and the like
• Scripting requirements - be sure anything you might need for an outside application (like WordPress) is there
• General advice

There's a bit more detail on each of the points to round out the advice.

Here I want to list all those things, but near to each of them I will give short explanation what is it and how CakePHP implement it. So, if somebody ask me what are those 10 things which drive me to choose this framework as my primary one I will answer with [this list].

Included in his list are things like it's MVC pattern, the object relational mapping, that it's easily extensible, has ajax support and makes the CRUD scaffolding easy.

It seems as if everyone is a Web publisher today -- from the habitual bloggers and online diarists to the companies running major news outlets, portals, and magazines -- and they're all using some kind of database-backed content management system (CMS) to do it. There are a lot of CMS choices -- Drupal, Mambo, Bricolage, WordPress, and Plone are some of the most recognizable names. While they all perform the same basic functions, you have to pick only one. How do you do it?

He goes through two different questions to think about before you settle on the one you'd like to use:

• What to look for - including the licensing, what language it's in, is the project active, is there support for it?
• Which is the right one for me? - does it have the features you want, is it 'just a blog' when you need 'just a blog', how customizable is it?

Check out the comments too for some great opinions already voiced.