Earlier this week, I announced a new site that I'm working on under the domain SocPub.com. What I didn't say in the announcement was which CMS I was going to use for the site. I also didn't say that my choice in the CMS version could be considered by some as risky. I have decided to use the alpha/beta/release candidates of Drupal 7 for the SocPub site.
At the start of every year, I like to resolve to read a number of IT, CMS, and business related books. The Internet is a good resource, but perhaps because I'm too old school I still like to learn a thing or two from a book. So far I have three books on my reading list for 2010.
I plan to review each of these books at a later date but since I'm a slow reader I thought I'd share them now. Links to the books go to Amazon for a possible purchase are our available in CMS Report's Amazon store.
Enterprise 2.0: New Collaborative Tools for Your Organization's Toughest Challenges
By Andrew McAfee
I waited for much of 2009 to see this book get published. This is the book for companies and organizations wrestling to understand the impact Web 2.0 and social media applications can have on their business. I had hoped to have read the book by now, but the holidays were too busy. You can expect that this will be the first book I'll review in 2010.
McAfee brings together case studies and examples with key concepts from economics, sociology, computer science, consumer psychology, and management studies and presents them all in a clear, accessible, and entertaining style. Enterprise 2.0 is a must-have resource for all C-suite executives seeking to make technology decisions that are simultaneously powerful, popular, and pragmatic.
This year, I had the privilege of participating as a member on the judging panel for Packt Publishing's Overall Best Open Source CMS Award. As I mentioned last month, WordPress was declared the winner of the award followed by MODx, SilverStripe, DotNetNuke, and finally XOOPS. Since the award announcement, I've had a lot of inquiries asking me how and in what order did I rank the content management systems. I decided to wait for a month before my posting my rankings of the Web applications because I wanted focus to remain on the declared winners and not my individual choices.
My rankings for the Overall Best Open Source CMS (with number one being the highest) were:
Each of the judges on the panel, selects their top three CMS from the five included in this category. The judges are given a lot of reign for how they rank the CMS and may consider a number of factors such as performance, usability, accessibility, ease of configuration and customization, scalability and security. Despite the criteria given, the fact is the best CMS is the CMS you determine is best in meeting your project requirements. In other words, you may find that all five CMSes in this category meet your project needs or in some cases none of the given applications will meet your requirements. Despite how I ranked the CMS you still need to do your own homework before choosing what your "best" CMS.
I'm one of the many CMS enthusiasts excited about CMIS. CMIS is the abbreviation for the OASIS Content Management Interoperability Services (CMIS). Please check AIIM's official guide to CMIS for further details.
Before you do go over to AIIM's site, you might want to also check out Stefan Waldhauser's "8 reasons why CMIS will transform the ECM industry" posted at Digital Landfill. I like reason number four:
4 -- No more lock-in to one ECM-vendor because of CMIS.
Until today the ECM industry was driven by high complexity and proprietary systems that prevented to switch to other vendors. Even when a vendor dramatically increased maintenance fees (many customers know what I’m speaking about) there often was no choice to go somewhere else because of the tight and proprietary integrations between the customer build applications and the ECM-infrastructure. CMIS will help separate the applications from the ECM-platform and so there will be no more lock-in to one vendor. Doesn’t that sound great?
I think the biggest thing CMIS offers is customer satisfaction in not having to choose one vendor over another. As I stated this morning on Twitter, I see CMIS as recognition that the "total enterprise solution" is a lie. I have yet to see an enterprise software package provide the complete solution that vendors often promise their customers. Somewhere in the product's life cycle the customer finds that they need more than what the current software and/or vendor can deliver but the customer also isn't ready to leave their current system behind. CMIS hopes to solve the migration issues involved with moving from one application to another by allowing both applications to work together.
There is a cost issue here with CMIS though and, so far, I haven't seem much dicussion on the subject. While CMIS allows more than one application to share and work with the content it will not always reduce costs and maintenance fees. The fact is CMIS may now require the customer to provide ongoing support for multiple applications and platforms instead of the single platform they were once supporting. In general, when the customer's IT group has to support additional applications they also need additional time and money required to provide that support. Just like the problem CMIS is trying to solve, CMIS will not always be the total solution to your problems.
Not having the opportunity to own an iPhone due to lack of coverage by phone carrier AT&T, I haven't been a smartphone user. Then a few weeks ago my carrier, Verizon, introduced the Motorola Droid and I purchased my first smartphone. Since then, I've been carrying the Droid where ever I go and taking full advantage of the phone's features.
"These habits and rituals, developed over many years now are hard to break. I find it quite staggering for instance that the collective wisdom of a very established global manufacturer is contained in folder after folder after folder of files on shared drives with seemingly very little actual captured knowledge, context or lifecycle management."
-James Hoskins, "#fixwcm – some thoughts from the front line…", 2020 Visions, November 5, 2009
Tony Pietrocola, Bridgeline Software, posted on their blog seven ways to "Avoid These Common Mistakes When Implementing WCM". Two of the tips he gives have been giving me trouble lately.
2. Have the requirements from all stakeholder groups been accounted for? One of the critical issues that sink CMS investments in the organization is missing all necessary input and buy-in.
We lasted nine months. That's right, for nine months we hosted our Drupal site with a shared hosting account. Last January, I knew we were taking a gamble but the monthly cost savings for hosting the site was just too tempting. In this end though, CMS Report was too busy and exceeded the shared hosting provider's CPU usage policy.
I do my best to keep my two IT world's separated. One of those worlds of course is my obsession with content management systems which includes this blog and numerous discussions with almost anyone interested in CMS. The second world is my IT position as a federal employee for a small government field office. In order to avoid conflicts of interest, rarely do I allow those two worlds to cross one another. You'll find very little mention on this blog of my work for the federal government. At the same time, very few people in my agency are even aware of my CMS side hobby.
Earlier this week, Lullabot's Jeff Robbins posted an article about his company giving Drupal on-site training to employees within the Department of Commerce. In his post Jeff discusses the interest those employees have in Drupal as well as mentioning that the door continues to widen for Drupal in the federal government.
We had a great week of on-site training at the Department of Commerce in Washington, DC last week. They've already launched recovery.commerce.gov in Drupal and they're currently in the process of rebuilding Commerce.gov as a Drupal site. We spent the week with their team making sure that they understood not only how to build and present a Drupal site, but also the benefits of the Drupal community. They're a smart bunch and it's always fun to watch the synapses sparking as people realize all of the ways that they can snap together Drupal's pieces to create interesting web functionality.
There seems to be quite a buzz around Drupal in the government and as the Commerce team walked around the building with Drupal books under their arms, they got lots of comments from people in other bureaus, saying, "Oh! Drupal! We're thinking about using Drupal." Word is starting to get around about Drupal as a great platform for government websites.
Jeff Robbins is correct in saying that until recently, there was a lot of hesitation to using open source CMS such as Drupal for government portals and content delivery. I know earlier this decade my agency's Webmaster had considered using Drupal before deciding to build the agency's own CMS in-house. During this time period Drupal 4.5 was available but while my interest in information systems was growing, I had never really looked into Drupal (Mambo was in the open source CMS headlines back then) . However, just the possibility of my agency considering the use of Drupal during that time helped motivate me to learn more about Drupal.