Bryan Ruby

My back hurts. As with the rest of the United States, my neck of the woods has received more snow and cold weather than one could possibly want for the winter season. Due to the constant snowfall, I have spent a number of my days clearing my driveway from snow with the help of my 15 year old snow blower. Several days ago, the snow blower's auger died on me leaving me with a useless rusting piece of machinery.

Auger Belts

1. Remove the plastic belt cover on the front of the engine by removing two self-tapping screws. See figure 23.

2. Drain the gasoline from the snow thrower or place a piece of plastic under the gas cap.

I received an email from someone that wanted me to talk about TYPO3 Version 4.5 LTS. The suffix “LTS” stands for “Long Term Support”. For the first time a TYPO3 version will be maintained by the TYPO3 Core Team significantly longer than the usual release cycle would suggest. In 2010 TYPO3 has switched to a fixed 6-month release cycle which means up to now support for a version was only provided for 18 months (only three of the latest three versions actively maintained). The LTS versions will be supported for at least 3 years thus offering a good option for users that don’t need or don’t want to update every 6 months.

TYPO3 is used for a great variety of websites ranging from the smallest private homepage up to large multi-server, multi-language enterprise portals. Upgrading for everyone is reported to be easy, since the development team focused on maximum backwards compatibility with older releases. This provides a very easy and stable migration path to TYPO3 Version 4.5 LTS.

Older features are still supported and the use of deprecated features can be easily tracked in a log file. If you're still stuck in the dark ages of the browser war, you'll also want to note that TYPO3 Version 4.5 LTS is the last release to support Internet Explorer 6 for the Backend.

New features and improvements found in TYPO3 Version 4.5 include:

• A fast and flexible pagetree based on, configurable Backend layout and rearranged editing forms for pages and content elements.
• The new LiveSearch box providing instant auto-completion. A similar technology empowers input fields to find connected records in a snap.
• The whole Backend gets an optical facelift. Icons, colors and the general arrangement of elements were streamlined. Many details were fixed to provide a more consistent appearance and workflow.
  

I like to keep things simple and prefer to use content management system (CMS) as the term used to describe the information system we use to manage all content. However, I will acknowledge that it is sometimes good to categorize a CMS by purpose. This differentiation of a CMS by purpose has given us subcategories of the CMS which include the enterprise content management system (ECM), the web content management system (WCM), and the social publishing system (social business system). In a press release this week, Alfresco introduced me to social content management, another new marketing term to describe a CMS with the purpose of managing social media.

Alfresco is tying to evolve the social content management system higher than the social publishing system within the information system food chain. If you ask them, a social content management system would do something much more than a social publishing system. I'm not convinced of that, but they do make a good argument.

Alfresco Enterprise 3.4 is purpose-built for managing content in a social world. Enterprises are increasingly deploying social business systems like Jive, Salesforce.com’s Chatter, Lotus Quickr, Drupal and Liferay, among others, in the hopes of making employees more effective. According to Alfresco, these social business systems are creating volumes of unmanaged content if left un-checked. Using open standards like CMIS & JSR-168, Alfresco Enterprise 3.4 is a content platform with a goal to co-exist with social business systems to help manage and retain the content created by social business systems.

The marketing team over at Alfresco are pure geniuses. In this case Alfresco is using the social business systems as another catch phrase to describe what I know to be social publishing systems. Alfresco on the other hand identifies their product as as a social content management system that co-exist to manage the social content created by all these other systems. A CMS that is needed to clean up after the mess created by all these other social publishing systems.  I'm not sure I buy the argument that there is much difference between a social content management system and a social publishing system. But I will bite that social content management has a much better ring to it than social publishing system or any other term we use to describe the management of social content.

From now on when I describe a CMS for the purpose of managing social content, I'll likely use the term social content management instead of social publishing system. It seems to be a more fitting term for describing the direction the CMS is currently evolving toward. So hats off to Alfresco for pushing this term in their marketing. In a CMS world where ECM and WCM can exist, I see no reason why there can't be a SCM. On face value, there is nothing wrong with this logic. Except, of course, I like to keep things simple and prefer to simply call all these information systems a content management system. However, who am I to argue with progress.

This week, Alfresco announced the availability of Alfresco Enterprise 3.4 for download. This new release delivers on Alfresco’s vision of providing the open platform for social content management by delivering both a more robust content platform for building any kind of content-rich application, along with a more social user-interface for collaboration and document management.

Last fall, I once again had the privilege of participating as a member of the judging panel for Packt Publishing's Open Source Awards. For the 2010 event, I participated by voting for the category of Open Source CMS Awards. In that award, the winner was declared by the panel to be CMS Made Simple, with SilverStripe as first runner up followed by MODx as second runner up.

I received a lot of inquiries asking me how and in what order did I rank the content management systems. Each of the judges on the panel, selects and ranks 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 including performance, usability, size and support from community, accessibility, ease of configuration, customization, scalability and security.

It has been my history to be transparent to all with how I rank each CMS as my vote will have some differences to those of the panel. This time around, I find myself hesitant and under personal protest with me providing information on how I ranked the five content management systems.

I question whether we're doing any good by declaring one CMS as better than another CMS. Dean Barker discussed on his blog some time ago this same uneasy feeling you get when you judge a CMS without having some reference to real world requirements. None of these content management systems would I consider losers and all of them remain worthy of future consideration. Yet, I'm disturbed that people will look at the numbers and interpret the results in a ways I never intended my rankings to be used.

My rankings for the Five Best Open Source CMS (with number one being the highest) were:

1. SilverStripe
2. mojoPortal
3. MODx
4. XOOPS and CMS Made Simple (Tie)

I'm not a firm believer in ties when it comes to ranking content management systems. Yet, this year I did just that for XOOPS and CMS Made Simple. All five content management systems that were reviewed I would consider as a candidate for a future project. None of the CMS would I consider a "last place" CMS so I refused to do so. It is also important to note that neither Drupal, Joomla!, or WordPress competed in this ranking as previous winners in this category duke it out in the Hall of Fame category.

While I try to do my best to cover some of the big names in content management systems, I think the best part about CMS Report is it has introduced to both you and me web applications that are just starting to become known to the CMS world.

Ryan Cramer recently introduced me to a relatively new CMS called ProcessWire. Ryan is so passionate about this CMS that he would like to now grow both the user base and the open source community behind ProcessWire. In Ryan's own words:

I'm a regular reader of your Twitter feed (which I enjoy a lot, so thanks for doing it).

I've been designing and developing CMSs for about 10 years now, and specialize in large scale content management solutions for several companies throughout the US. I recently released an open source CMF/CMS project called ProcessWire.  As a user of multiple CMS platforms, I built this tool to be one that fills my own needs where other products don't, and I think it's fairly unique in several aspects (especially with regard to the API).

I'd like to grow the user base with the goal of getting more people involved in the project itself. Now that we've gone past the developer preview stage, I'm starting to look at how to get the word out...

Thanks,
Ryan

ProcessWire 2.0 is very similar in look and function to Dictator CMS (2003) and ProcessWire 1.0 (2007), both of which are still in use on many sites today. Despite intentions to do so, neither product was ever released open source, except for the projects the author used it with. ProcessWire 2.0 is the first GNU/GPL licensed version, and it is architecturally stronger than the CMSs that preceded it.

A number of  sites have already been developed with ProcessWire including such sites such as Lost River Winery, TripSite.com, Island Hideaways. Honestly, I was impressed with the design quality and functionality of the sites developed with ProcessWire.

All in all, if you're bored with your current CMS or looking for something different I think you should look at this most promising CMS, ProcessWire.

After three years of open source development, Drupal 7 has finally been released to the public. As Ric Shreves previously mentioned in his article, there are literally hundreds of changes in Drupal 7. I've included below a list of the more significant changes from Drupal 6 to Drupal 7. I've also included a nice Drupal 7 marketing video via Jeff Robbins at the bottom of this post. Also there is always official Drupal 7 announcement for additional information on this latest version of Drupal.

Barring any unforseen changes to how I manage this site, I expect we will be upgrading CMSReport.com from Drupal 6 to Drupal 7 within the next few months. I've been playing with Drupal 7 off and on this past year, but I must confess I haven't been as aggressive in my testing of this version of Drupal as I was with Drupal 6.

Some of the more significant changes in Drupal 7 since the release of Drupal 6 include:

1. Overhaul of the User Interface

Work has been done to improve the user experience and administration interface. The new administration theme "Seven", the overlay module, the dashboard and the configurable shortcut bar, all lead to a much more user-friendly interface.

2. Custom Fields

Drupal 7 bundles in the ability to add custom fields, similar in functionality to the Content Construction Kit (CCK) module. However, fields are no longer limited only to content types; they can be added to users, taxonomy terms, and other entities. Fields also have support for translations.

3. Image Handling

Drupal 7 brings native image handling to core. Image fields may be added to content, and have image styles applied to them, such as scaling, cropping, and other effects.

What a great year 2010 was for content management. Open source CMS projects seemed to have grown up this year while proprietary systems appeared to continue in their evolution. While social publishing systems may not have conquered the traditional content management system, the CMS definitely took notice by integrating as many social media features developers could come up with.

Below are the top ten stories of 2010 that were posted here at CMSReport.com. The stories in this list were ranked by the number of views per month since the articles first appeared at CMS Report. 

Top Ten Content Management Stories of 2010

1. Someone does another Drupal vs Joomla comparison
2. Open Source versus the Enterprise Solution
3. Ten Content Migration Tools to SharePoint Platform
4. Drupal themes go nuclear with Fusion
5. SilverStripe CMS becomes the first Microsoft Certified open source web app
6. Denial of Service on an Apache server
7. Guidelight Business Solutions video of DrupalConSF 2010
8. Sharepoint 2010 vs WCM Platforms
9. We Hear You: Our spam filtering needs to be improved
10. The MODx Revolution 2.0 Interviev

As you can see, stories on Drupal, Joomla!, Sharepoint, SilverStripe, and MODx brought a lot of visitors to the site. Not all the stories listed above would have been one of the ten I would have personally picked, but I'll respect the numbers behind their ranking. I personally, don't like "versus" articles yet readers seemed to flock those articles. Unfortunately quality of writing doesn't appear to always matter as there were some very well written articles we posted in 2010 that didn't make this list.

The year 2011 will undoubtedly bring change and new stories to the world of content management systems. I think the year will also be a year of decision for the direction we take CMSReport.com. I feel as if this site of ours is stuck somewhere between our roots as a niche blog and a potentially popular CMS news site. I'm hoping we make some changes in the new year that all our readers can appreciate and value.

David Bobzien: WordPress Analytics: What You’re Doing Doesn’t Measure Up via WordPressTV for WordCamp Las Vegas 2010.