Acoustic Content (formerly IBM Watson Content Hub) vs Magnolia

• It has a wide variety of built-in API calls.
• Building unique pages is simple and straightforward and requires only basic fundamental knowledge to get started.
• More advanced API calls can be developed simply.

Read full review

• The usability of Magnolia is appreciated, a content editor easily learns how to manage the content in two hours only.
• Magnolia is open, flexible and extendible and it is possible to modify or improve the standards features. Using Java API, REST, SOAP, CMIS, XML, etc. makes it possible to integrate other software or legacy data.
• Magnolia as a modular architecture, a module has its lifecycle, configuration, version handing and dependency: this is a good approach for package content and functionality.
• Magnolia is written in Java, the platform of choice for enterprise IT systems. It is scalable, stable and secure, and Magnolia separates the staging from public environment.

Read full review

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

Read full review

• Give users specification details and or tips for module items and fields (ie. explain what the fields would do to the front end-user)
• Batch upload drag and drop for assets/images
• [The] simpler way to find out the URL of a page without publishing for both EN/FR users
• No way to revert to past versions of a page that hasn't been published live
• A way to copy a specific module on a page with all the fields and settings completed and paste it to a different page

Read full review

• Freed up user time to call a variety of applications quicker.
• Allowed developer an easier tool to integrate other applications for end users.
• Allowed us to have a single method of application implementation and usage that is easier to debug, saving time.

Read full review

• Has provided our organization with an easy-to-use CMS. Even inexperienced web page builders can create content.
• Has allowed us to create a bilingual website that reaches a large audience while meeting language requirements.
• Common templates have allowed us to create a cohesive website.

Read full review