Language Selection

English French German Italian Portuguese Spanish

Selecting an Open Source Content Management Solution

Filed under

When it comes to Content Management Solutions (CMS), “one size” does not fit all. When considering open source CMS for a real-world client experience, it’s necessary to focus on the project needs, evaluate various CMS solutions in the context of these project needs, and to explore experiences with the strengths and weaknesses of the solutions.

One example we found was at the Sports Club/LA, a company that operates upscale fitness facilities in numerous cities including Boston, Manhattan, Miami, San Francisco, and Los Angeles.

Its new management decided that this situation had to change, and commissioned a new e-business Website to drive online sales and generate leads through the Web, and also reflect the upscale nature of the brand with an attractive design.

CMS Evaluation
Based on these criteria, it was necessary to research CMS offerings. A shortlist of four was chosen based on market leadership: Drupal, Alfresco, Joomla, and Liferay. A review of articles on the Internet and internal tests resulted in the following conclusions:

More Here

More in Tux Machines

Data indicates that Android picked up global market share from iOS last month

Tracking mobile web traffic, NetMarketShare computes the market share for mobile operating systems. Based on the data from last month, Android was able to widen its gap over iOS globally. Considering that the Apple iPhone 6s and Apple iPhone 6s Plus weren't launched until September 25th, the recently released phones accounted for a miniscule part of the data. The new models won't have a major effect on the results until the figures for this month are released. Read more

RapidDisk / RapidCache 3.4 now available.

RapidDisk is an advanced Linux RAM Disk which consists of a collection of modules and an administration tool. Features include: Dynamically allocate RAM as block device. Use them as stand alone disk drives or even map them as caching nodes to slower local disk drives. I pushed 3.4 into the mainline earlier this morning. Changes include:
  • Added ability to autoload RapidDisk volumes during module insertion.
  • Fixed bug in RapidDisk (volatile) volume size definition across 32 to 64 bit types.
  • Making use of BIT() macro in the driver.
  • Removed RapidDisk-NV support. It was redundant with the recently kernel integrated pmem code.
You can pull it from the git, yum, ZYpp & apt repos or download it from the SourceForge project page. To stay updated, you can follow the RapidDisk Google+ page.