Another happy customer | TrustRadius

Use Cases and Deployment Scope

We use Paligo for our technical documentation (not the rest of our website). This includes:

HTML output for our public website (help center)
PDF output for selected customers or internal use.
In the future, we plan to allow users to log in to the doc portal so they see only the documentation that is relevant to them.

Pros and Cons

Content re-use
Full flexibility in HTML (and other) output

In my opinion, the user dashboard has minor issues
In my opinion, reviewing is clumsy - reviewers need changes highlighted and view everything in preview mode only
Better documentation - In my opinion, we have to rely too much on our customer service rep

Most Important Features

content re-use
unrestricted content
accessible XML source files

Return on Investment

Hard to gauge at this early stage - our new layout is much more user-friendly than what we had before

Usability

8

Some aspects of the user dashboard require a fairly steep learning curve. Hard to say how that stacks up against the competition.

Support Rating

10

The support team is great - but sometimes our questions were simple enough that the answers should have been in the documentation.

Alternatives Considered

ReadMe, Contentful, PTC Arbortext, Flare, Acquia DAM (Widen), Drupal and 360dialog

Web server is under our control
Content editable via dashboard and also APi
Full support of DocBook
XML source files
Reuse of content
Publishing on demand
Output to PDF and HTML

Key Insights

Do you think Paligo delivers good value for the price?

Yes

Are you happy with Paligo's feature set?

Yes

Did Paligo live up to sales and marketing promises?

Yes

Did implementation of Paligo go as expected?

No

Would you buy Paligo again?

Yes

Likelihood to Recommend

It suits our needs very well - I have not considered other possible uses.