I have created a case study for cmsmatch.com, http://drupal.org/node/618430, and would like it promoted to the frontpage.
CMS Match is a free community-driven software comparison website. It has currently integrated Apache Solr faceted search, Opencalais/RDF/Marmoset and other interesting Drupal extensions. The current database compares over 1,000 CMS, shopping carts and discussion boards.
The main selling point about this site is that users can update the listings/scores all by themselves. Slowly the database will grow. Hoping to become the #1 comparison site for CMS in the world.
Of course it lists Drupal and Acquia, which are ranked in the top 10 ;)
Thanks!
Mathijs Koenraadt,
CMS Match administrator
PS Attached images should show in top right corner of the article. I added 
tags.
| Comment | File | Size | Author |
|---|---|---|---|
| CMS Match - Software Comparison 2.0 | 53.25 KB | Anonymous (not verified) |
Comments
Comment #1
gdemetI'd be more than happy to review this, though the exact date of promotion would depend on when various other items before it in the queue get promoted (assuming there's at least two +1's from different members of the webmaster's team).
One question though, on the page for Acquia Drupal are you really sure you want to be referring to it as a "fork"? I suspect that most folks around here would call it more of a "distribution". ;-)
Comment #2
gdemetComment #3
Anonymous (not verified) commentedFeel free to publish whatever date available, if it gets thumbs up... And you're right, I'll edit that Acquia page! Thx
Comment #4
gdemetOkay, I've gone through, made a couple of very minor text tweaks, and turned on Full HTML format so the image appears on the teaser. Can any other site maintainers weigh in and/or offer their +1s before we put this on the schedule?
Comment #5
gdemetThis case study has been sitting for a couple of weeks now with no feedback from any other site maintainers. I'm going to give folks another couple of days to weigh in before removing it from the schedule and marking this issue "won't fix".
Comment #6
gdemetGiven the lack of feedback from other site maintainers, it doesn't look like there's any interest in promoting this case study; moving to "won't fix"