Acoustic Content vs. eZ Platform

We can organize all our content easily by uploading content files and other digital assets. CMS smart AI generates metadata by tagging them automatically which helps us to sort our content into different categories. CMS content modeling feature helps us to visualize our content structure, assemble them in an intelligent manner and reuse the content whenever we want to for different purposes.

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?

• Creating separate pages is easy and straightforward and only requires basic basic knowledge to get started
• Advanced API calls can be easily built.

• 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.

• The organization of the application is poor and some elements could be more easily accessible not buried in menus.
• There is little to no community around the application and what does exist is out of date.
• Does not work well with our IBM applications as well as you would expect, which seems a common issue with IBM products.

• 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.

Acoustic Content stands out mainly in 3 areas, Digital Asset Management system AI Based metatags More secure CDN and REST API to share content All these three features play a huge role in Acoustic Content CMS in terms of finding matching images for our content, categorize and sort our content automatically and finally secure way to publish our content.

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.

• Approved developer is a simple tool for integrating other end-user applications.
• It has allowed us to have one-stop-shop and easy-to-use debugging, saving time.

• 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.