CoreMedia vs. eZ Platform

I think this CMS is best suited as an enterprise level system. For small, or simple sites, there are better options, but for large high-traffic sites, this is a great CMS.

For a new site: 1. Are there any hosting requirements? eZ Publish works best on a traditional LAMP stack. 2. What is the expertise of the development and systems administrations individuals? There should be some PHP development experience and a solid level of Apache and MySQL hosting. 3. Who will be managing the content of the site? What is their bandwidth for training? For ongoing content changes?

Incentivized

• Allows many staff members to contribute content to various portions of our website, and allows our Electronic-Communications staff to delegate tasks to these various staff (diffusing the work-load).
• CoreMedia allows for easy creation of different types of content (like teasers, articles, download objects, links, etc). Permission levels can be set, so only certain staff can upload content such as photos, videos, or audio files.
• The CoreMedia workflow process is easy to understand and follow. Once a staff member has submitted content for publishing to the web, they can then see who it's been assigned to for review, and at what time. You're able to leave detailed notes and stay abreast of where the workflow is at any given time.

• Content Taxonomy: Content is managed in a tree. Though taxonomy vs folksonomy is a near-religious debate among professionals, clients seeing the system for the first time just seem to "get it" more often.
• Content Flexibility: Common content types such as blog posts and articles are available out of the box. However, customizing these and creating new content types is very easy.
• Developer Friendly: Developers need only a little PHP experience to get started. Of course being an expert doesn't hurt and opens the door for the development of custom modules.

Incentivized

• Early learning within the company was slow.
• We elected a customized version of CoreMedia - which in the end may not have been the best decision.

Incentivized

• The template language: Outputting content or doing something special with it requires use of the templating language. Myself along with other developers I have trained, found this to be one of the biggest hurdles.
• Layout of physical files: The system decides what settings files and templates to use based on a hierarchy of modules. The same file can exist in multiple modules and you can find yourself deep within very similar looking folder structures, causing confusion during debugging.
• Community: eZ has a solid set of community contributors but the gap between it and Drupal or Wordpress is pretty large.

Incentivized

CoreMedia continues to refine and deliver new features. They also explore new technologies and trends, like social media integration. The platform is solid and growing. We are also slightly locked into using CoreMedia. Migrating such a large amount of content to another system would likely not be feasible or prudent.

Set aside more time than you think you need to migrate content. That is the hard part. Implementing the technology is easy.

While CoreMedia has a better workflow, django CMS has a much easier user interface, wysiwyg editor, and is superior on every other level. Django CMS is easier to teach and support, easier to manage and develop, and provides much more flexibility in the development and design areas.

Incentivized

eZ Publish isn't as large in community size and number of installations as other content management systems. However, it's just as capable and met our needs:

• Developers, system administrators, and project manager can all speak the same language during the development and maintenance cycles of a site.
• End-user training is very straight-forward.
• Vendor support is available.
• Client IT departments can access if need (developers/designers/sysadmins).
• The community is there (forums) and there are solid contributions (extensions) from both the vendor and the community.

Incentivized

• Increased employee proficiency compared to nothing at all. I really don't have anything else to compare it to though.
• Reports from Core do not help/.

• Common knowledge: By making eZ a core offering, developers, system administrators, and project managers were able to communicate with each other effectively.
• Training: Due to its content taxonomy, end-user training often went well.
• Support: In our case, we had Gold support from eZ Publish which saved time and helped with customizations.

Incentivized