We've added several of these to the matrix. However the "good upgrade tool" and "ease of install" type questions are too subjective and relative to the person, so they will not be added.

What's easy for me might be hard for you and so on.

The "webstats per page" question is a little too specific to your needs. The matrix is here to give you an idea of the features of a given CMS. IE, does it generally have a feature or not. It is not a be-all end-all. Once the matrix narrows the scope of choices for you, you still need to independently verify that the features you want are in the product you choose.

Could you please provide descriptions for each of these so we know what you're asking?

Also, we only ask yes/no type questions. "Ease of installation" is a hairy question that could take an entire essay to explain. Also, it's very relative depending upon experience of the installer, operating system, prerequisites, etc.

Supports load balanced web servers?
Can the system work on/with load balanced web servers? With 4 load-balanced servers is there one database server needed or 4? Stored images: where are they stored? In a separated database server or in one of the Load balanced servers? In the latter case how are we getting the images on all balanced servers?<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Web stats per page?
That you can follow where people go on the site. Web statistics do not always give us a good idea for dynamic pages.

Administrative warnings (email)
When something goes wrong in the system it would be nice if administrators do get email warnings so they can act.

Ease of installation/impact on front-end
Rephrase: Good upgrade tool available?
When a new version is installed the impact to the live environment is not always clear. I would like to know if upgrade tools are available. To reduce installation/testing time. Every new build needs testing in critical environment. We need exactly to know what is happening with the current data.

New point: Can export data from staging to Production server?
Can the application deal with exporting/syncing from Staging to Production server? Do you need to enter all data into the live system again? Or is there a "data to live" button?

We can say that WebGUI is not easy to install and Mambo is easier. Perhaps a scale from 1 to 10 can be used?

Thanks,

         Bastiaan

XML / XSLT Support would be nice to know

And whether it is standalone CMS (separate from content/delivery) or whether it has to do content delivery too. (many people have existing web delivery systems in place) and simply need to manage their existing content

We'll be working on the Matrix this weekend, adding some new features and CMS's. I'll add these to our todo.

re: "ease of use" etc

You have user ratings for the subjective fields. Do you HAVE to only have tick boxes in the search? You could have a Selection box with 1-10 listed. I could select "7" and only have CMS listed with ease of use >= 7.

I'd also like to see a selection box for PHP/ASP/PERL etc - And "MySQL/Postgres/Oracle/Flatfile" etc

How about an extended explanation for the current features in the matrix?.

Some of them are self explanatory but others require a glossary.

I think it would enhance the usability and minimize possible confusion.

Never mind, current mouse over is fine (too eager to post).