Acoustic Content vs. HCL Digital Experience

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.

HCL DX does really well at managing and maintaining the site. It allows the business to basically maintain the site while IT spent time developing new and enhanced functions. The main issue I currently have with HCL DX is not directly with the product but it does play a role. It is difficult finding skilled resources to support HCL DX in my experience.

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

• With Version 8.5, IBM Web Content Manager introduced in place editing capabilities which allow authors to make content edits on sections of the page instead of going to the content itself. This feature allows authors to make changes in context of the page and preview changes within the actual look and feel of a live page.
• Projects provide a collaborative atmosphere for the author community so that authors can interact and work as a team to manage inter-dependent content changes under one project and publish all changes at once, instead of working separately on individual content changes. This brings awareness across authors in an organization and easy knowledge share.
• IBM Digital Data Connector is a cool feature that allows [users] to integrate external content sources onto the portal using IBM Web Content Manager presentation components. This allows UI/UX designers to present integrated external data in any manner they want, manage UI changes with an underlying approval process and leverage syndication to push changes live immediately.
• IBM Web Content Manager offers a targeted content feature that allows business users to deliver personalized content to customers based on customer demographic information, browsing history and other transaction related information. Any rules created follow the publishing process thereby making it just a configurable item resulting in less turn around to turn on the feature on a website.
• IBM Web Content Manager offers 'multi lingual solution' out of the box which allows content creation for almost all popular languages.
• Syndication feature has improved a lot and it now provides a detailed views comprising of 'failed items', 'items that have syndicated successfully, 'items in queue'. Failed items view provides detailed and clear cut information of what resulted in failure helping IT to troubleshoot problems easily.

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

• IBM Web Content Manager should provide some easily usable connectors through a GUI to connect to bring content from custom data sources including connecting to Salesforce and custom databases.
• Should further optimize and enhance creation of rich and responsive content driven UIs on various digital channels.
• Should further optimize and enhance content personalization features.

IBM products always moves forward to adapt to new requirements and technologies. I have used versions 6, 6.1, 7 and 8 of IBM WCM, and I know IBM is ready to revamp the tool based on emerging needs, and still provide the capabilities to migrate your old system to the newer versions.

New versions has increased user experience facilitating usability.

We had some issues related with performing and the support was suitable and sucessful.

Implementation was successful due to Websphere application server used.

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.

Magento and Prestashop are E-commerce CMS platforms. They are used in a different scale of application than WCM.

Concerning Joomla, it's a useful CMS forsmaller website. Once again this is an other scale of application than WCM Liveray can compete WCM 7 concerning the : ¤ specific development ¤ security ¤ responsive

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

• Negative: Very complex architecture for on-premise deployments (too many servers to installed)
• Positive: Easy customization
• Negative: Architecture limited to cloud solutions
• WCM is an old product and needs an update
• Blog, and community are not integrated in Digital Manager for discussion
• Templates are not available to integrate basic services (FileNet, more complex BPM , e-commerce)