HCL Digital Experience vs. Paligo

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.

Incentivized

Paligo is particularly well suited for developing similar document sets for multiple products or product lines. It is not a page layout application, so don't expect the same capabilities as popular applications for graphics-heavy documentation. With some up-front time developing good layouts, however, Paligo does manage to create very usable PDF output for customer-facing documents.

Incentivized

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

Incentivized

• The review mode is super convenient. Comparing a snapshot of the previous versions with the current one clearly outlines the respective changes and reduces the necessary content to review tremendously.
• The option to reuse text fragments is another handy feature. Text fragments will be updated whenever the original text fragment is altered is also extremely helpful.
• Managing a content's structure was never easier. An intuitive drag & drop functionality allows you to design your document's structure however you like.
• You can also fork content, in addition to reuse text fragments. This is another helpful option that no longer requires you to create repetetive chapters over and over.

Incentivized

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

Incentivized

• The amount of CSS/JS required to customize a site's appearance can be cumbersome
• Product documentation can be lacking, specifically with integrations; in some cases, support offered no real help when trying to solve a problem with an integrated service
• Some features require extensive development experience to use, which can sometimes be an obstacle to less-experienced team members

Incentivized

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.

Paligo single-sources beautifully. Allows for customization. Has the best translation features. Has the best support services.

Incentivized

New versions has increased user experience facilitating usability.

Generally, I'm very happy with Paligo and the productivity gains that I get from using it. There are a few arbitrary limitations on structure, and when applying conditional formatting, that I don't really understand. Unlinking / editing reused text uses this broadly inscrutible colour-coding that I just hate. It would be nice to double-click a component, make edits, then respond to a popup asking if I want to confirm the edit for all linked content, or unlink this instance. Likewise converting from an informal topic insertion to duplicates of its raw contents.

Incentivized

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

All the support requests I've submitted have been resolved in one way or another. Sometimes it takes some back and forth, which is to be expected. This is where being on a different continent becomes a drawback. Since we became Enterprise users, we've also had an additional level of help and support from a dedicated account manager in the US, and the resolutions seem to come more quickly

Incentivized

Implementation was successful due to Websphere application server used.

Everything went well

Incentivized

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

We moved from Flare to Paligo. One of the main reasons was the fact that Paligo is a cloud product. Collaboration with anyone outside of our team was more difficult with Flare. Also, maintaining a server for Flare content was going to become an issue, and overall I felt the Flare desktop product was prone to errors and issues. The flexibility of assigning Paligo licenses was a huge factor, as was the stability of the cloud platform.

Incentivized

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

Incentivized

• I am not involved in the financial decisions for my company regarding Paligo; the decision to migrate our content to this environment predates my hiring. However, I know that the migration effort from WordPress to Paligo was an initially heavy lift, but any content migration effort would be. I believe that ultimately, getting our content out of WordPress was a positive move, and I look forward to seeing what Paligo will help us accomplish in the future. Sorry, no hard numbers from me. :)