OpenText's Web Experience Management is part of the Customer Experience suite and is based on the Vignette product that OpenText acquired in 2009.
N/A
Paligo
Score 9.1 out of 10
N/A
Paligo is a component content management system (CCMS) that helps teams manage complex technical documentation through structured authoring, content reuse, and controlled publishing.
$4,800
per year per seat
Pricing
OpenText WEM
Paligo
Editions & Modules
No answers on this topic
Professional
from $4800
per year
Business
Contact Sales
per year
Enterprise
Contact Sales
per year
Offerings
Pricing Offerings
OpenText WEM
Paligo
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
OpenText WEM
Paligo
Features
OpenText WEM
Paligo
Security
Comparison of Security features of Product A and Product B
OpenText WEM
8.5
2 Ratings
4% above category average
Paligo
-
Ratings
Role-based user permissions
8.52 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
OpenText WEM
8.2
2 Ratings
6% above category average
Paligo
-
Ratings
API
8.52 Ratings
00 Ratings
Internationalization / multi-language
8.01 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
OpenText WEM
7.9
2 Ratings
1% above category average
Paligo
-
Ratings
WYSIWYG editor
7.42 Ratings
00 Ratings
Code quality / cleanliness
8.02 Ratings
00 Ratings
Admin section
8.02 Ratings
00 Ratings
Page templates
7.52 Ratings
00 Ratings
Library of website themes
8.52 Ratings
00 Ratings
Mobile optimization / responsive design
7.52 Ratings
00 Ratings
Publishing workflow
8.02 Ratings
00 Ratings
Form generator
8.52 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Areas where OpenText WEM is well suited 1. Improved digital/web presence of the organization's leaders globally. 2. Established the leaders as go-to experts for thought leadership and domain knowledge among C-level executives of related industries. 3. Amplified the client’s marketing and branding efforts. 4. Customer engagement reflected by interaction count on social media—likes,comments and conversations.
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.
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.
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
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.
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
We have choosen OpenText WEM against other vendors because : 1. Helped client reinforce brand image through unique design language and templatization of collaterals, consistent messaging, and regular competitor benchmarking. 2. Enables lead generation through high-quality gated collateral, product videos, etc. 3. Senior management and sales lead meet client regularly for project review meetings and feedback on engagement
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.
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. :)
