Sitting on my desktop the past few weeks has been an eBook from the Aluent Group, Drupal and Joomla!: A Comparison of Project Processes and Costs. I probably would have not read this eBook if it wasn't for an acquaintance of mine, Justin Kerr, letting me know that he was a co-author of the book. I'm lucky to have read the book because I think Justin Kerr as well as co-authors Robert Nowak and Jet Pixel have hit a home run in their review and comparison of Drupal and Joomla.
Writing a comparison of any two content management systems can be challenging. This is especially true when the CMSs in the comparison are open source and each CMS has a legion of followers ready to pounce on anything you write that they perceive as false. For the reviewer, there is probably no better two open source CMSs to compare that can provide so much reward or risk than Drupal and Joomla. If you're lucky, have your facts in order, and the mood is just right then you too can take the Internet by storm just like I did in 2006. Don't do your homework and you will fail a miserable writers death.
Drupal and Joomla!: A Comparison of Project Processes and Costs is probably one of the most well-written comparisons between the two CMS platforms that I've read in a very long time. The authors' intended audience for this comparison include system implementers, IT department heads, creative agency owners, multimedia department leads and Web site stakeholders who are faced with a choice between Drupal and Joomla. In this free eBook the comparison made is between Drupal 7 and Joomla 2.5 with the most significant metric used in this book being cost not in terms of money but in hours to accomplish the various tasks.
A few days ago, WordPress 3.5 was released and I originally planned to write the typical "what is new in WordPress" article similar to what I've done in the past for CMS Report. However, I thought this time around I would also discuss how I'm using WordPress to support the website of one of my favorite photographers, Karen Ruby of Dakota Imagery. Certainly, in this article there is no cause for you to suspect my opinions are biased with regard to her photography skills despite the fact we've been married for 11 years and she is the mother of my child. In this article, my goal is to not only provide WordPress and CMS users something interesting to read but also to point photographers to a WordPress package that my wife and I have found works quite nicely to support her photography business.
As I'm writing this article, I'm currently in the process of updating my wife's WordPress website from WordPress 3.4 to WordPress 3.5. My wife is a photographer that over the years has evolved from amateur status to professional. When it was time to build her a new website (she had been using a SaaS site heavily weighed in Flash) we decided to keep it simple and use WordPress. Updating WordPress to the latest version only takes a click of the "Update Now" button and you're good to go. The process is generally painless and she usually doesn't require my assistance, but this time around we needed to wait on the availability of a newer version of Photocrati compatible with WP 3.5 before updating.
I do not know when it exactly happened, but a number of years ago I decided to become a pacifist. I am a pacifist that is in the war of open source versus proprietary. In my opinion, the debate over licensing and software development processes is only mildly interesting as it is the quality of the end product that matters to me most. I walk the fine line of being an advocate for open source and a defender of proprietary software. Admittedly I've confused a lot of people that have chosen to take sides in this war. However, there is always room for reasonable civil discussions of any topic when new data and new perspective is given. This is perhaps why within the past week I enjoyed reading a commissioned study conducted by Forrester Consulting on behalf of Acquia that shows the value of open source without necessarily attacking the value of proprietary software.
The independent study conducted by Forrester is titled “Is It Time To Consider Open Source WCM For Digital Experience?”. Given that the study is being promoted by Acquia, an open source Drupal company, it shouldn't be surprising to you that this paper highlights the benefits of open source web content management systems (WCM). However, the author of the paper does this in way that that doesn't also dismiss the value of proprietary systems. This paper is an invitation with business reasons given for IT shops that for one reason or another remain proprietary to start considering using open source solutions. That soft sell in my opinion will win over more customers than the doomsday ideologies we often hear from both open source and proprietary proponents.
For a second year in a row, I along with CMS Report was invited to cover Liferay's North America Symposium which is being held this year in San Francisco. During this morning's keynote speech by Bryan Cheung, Liferay CEO and founder, I couldn't walk away from the presentation without recognizing the difference a year can make for one company. Something has changed for Liferay and the many partners and associated vendors that are represented here at this conference. Liferay has grown up, people are ready to talk business, and they're once again ready to talk about the importance of open source and community which makes this all happen.
This morning, Liferay released some startling numbers on just how good business is in terms of growth for the Liferay ecosystem. Consider some of these highlights related to the announcement:
Two years ago I began a process to consider how best to evolve CMSReport.com beyond where it is today. I've known for some time that I needed to take some risks, get out of my comfort zone, and perhaps change how I maintain and run the site. Given the opportunity and in the spirit of taking risks I've decided to no longer run CMS Report on Drupal. That's right, after running this site on Drupal for more than six years on Drupal I've decided to use another content management system.
For those that don't want to be left hanging, I mention the CMS I've chosen to run the upgraded site on toward the end of this article. In a separate article I'll get into the specifics for why I decided on this other CMS and discuss the strengths and weaknesses of both information systems.
My primary objective with this post isn't to talk about another CMS, but instead to focus on Drupal and reflect on how much I owe a debt of gratitude to the Drupal community. I also want to make it clear that my decision to use another CMS is not a reflection of my opinions regarding Drupal. On the contrary, I have a number of past and future projects where Drupal remains the solution for my content management needs.