Paligo

Paligo

About TrustRadius Scoring
Score 10.0 out of 100
Paligo

Overview

Recent Reviews

Reviewer Pros & Cons

View all pros & cons

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Paligo, and make your voice heard!

Pricing

View all pricing
N/A
Unavailable

What is Paligo?

Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

12 people want pricing too

Alternatives Pricing

What is MadCap Software?

MadCap Software, headquartered in La Jolla, offers MadCap Flare, a help authoring and technical writing tool featuring onboarding and support from MadCap, and a set of modules for designing advanced guides, aids, and web or application help aids.

What is Confluence?

Confluence is a collaboration and content sharing platform used primarily by customers who are already using Atlassian's Jira project tracking product. The product appeals particularly to IT users.

Features Scorecard

No scorecards have been submitted for this product yet..

Product Details

What is Paligo?

Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.

Paligo Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Comparisons

View all alternatives

Frequently Asked Questions

What is Paligo?

Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.

What is Paligo's best feature?

Reviewers rate Support Rating highest, with a score of 9.9.

Who uses Paligo?

The most common users of Paligo are from Mid-sized Companies (51-1,000 employees) and the Computer Software industry.

Reviews and Ratings

 (5)

Ratings

Reviews

(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Rachel Cheyfitz she/her | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
1. PDF & Word generation to enable partner rebranding.
2. Push to Bitbucket for HTML5 embedded.
3. Push to Zendesk.
  • Zendesk integration is fantastic.
  • Single sourcing is amazing.
  • File management is easy and intuitive.
  • More flexible PDF formatting.
  • Self hosting platform.
  • Bi-directional open source repo syncs for true CI/CD.
  • API integration.
For any cloud-based documentation needs for any size company, if single sourcing is a priority, Paligo exceeds its major competitor. Because it was born in the cloud, its cloud-based features make it far more intuitive.
Rochelle Fisher | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use Paligo as our mission-critical authoring tool. It is a CCMS that enables our globally diverse team to work together to create various documentation deliverables in a topic-based method, with different writers working on the same publication, the same chapter, and sometimes the same topic in an efficient and consistent manner. It is based on the open-source DocBook schema, so if you change your mind a few years down the road, you are not locked into Paligo but can migrate with minimal expense and time. Paligo does single-sourcing better than other CCMS tools, creating beautiful PDFs out of the box and with easy customization, HTML5 for product Help, Word, SCORM, and more. It integrates perfectly with Zendesk, letting us push out 100s of new articles and articles updates in minutes. It has integration with AWS S3, GitHub, Memsource, and many other third-party tools for delivery and storage. L10N features are built-in and easier to use than in other CCMS and CMS tools. Variables are centralized and easy to manage with variable sets and variants for parallel publishing to OEMs and simultaneous versions. It has an easy-to-use XML interface if you want to get into the backend, and a nice WYSIWYG interface if you want to create content simply. The best thing about Paligo is its Best-In-Class Support and Customer Success. Actually, it's everyone at Paligo. Though Paligo has grown in the past couple of years, it still offers the awesome responsive expert solutions that it did when it was newer. For any team of technical writers, I highly recommend Paligo.
  • Single-source quickly and well out of the box.
  • Attributes in the content for conditional publishing.
  • Quick previews with publishing and variable settings, for efficient debugging.
  • Responsive expert support.
  • Extensive integrations.
  • Re-use features for consistency among writers.
  • Review features.
  • Translation features.
  • Push to Zendesk can add new image files each time or delete all attachments. Missing feature to delete only image attachments and keep external attachments (more of a Zendesk issue than Paligo issue).
  • Role-based access control.
  • Mirror servers, so that team members in different continents do not have a slower connection to the instance on the cloud.
Paligo is less suitable for solo writers unless you are a contractor with many customers, in which case it would be a great tool! For teams, this is the best CCMS I have used (compared to AuthorIt and Flare) and is much better than Word, FrameMaker, or similar, which are not designed for team use. The biggest reason for going with Paligo is the people. I've never had such a positive experience with any company's support. They are fast and give great help. When running into issues with integrated platforms, they don't say they can't help - they just take on the problem and send a solution. Everyone at Paligo listens. And they follow up with real actions. I would recommend Paligo for this reason to any technical writing team.
Monica White | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
We use Paligo in the Technical Documentation department to structure and publish the software guides. We use the Salesforce integration to push the content to Support and the HTML5 publication capacity to publish directly to internal access.
The ability to cross-reference and reuse content allows our technical writers to be succinct in topics while still presenting useful information across multiple products with a consistent message throughout.
  • The topic/publication structure is quite graceful. It makes setting up an outline of content quite intuitive, and after the tools are identified and defined, it's much simpler to set up a large document and work with others to produce it.
  • Strict field definitions and use cases make topic structuring inherent in the workflow, which brings more attention to content handling. The train of thought required to utilize the tool also improves the train of thought required to focus the content, making for a better ultimate publication.
  • The output capabilities and Salesforce integration make publishing the files very easy.
  • The learning curve is a bit steep, especially for anyone who's never worked in a true content authoring tool before. It takes a bit of work to move from a Word atmosphere to Paligo, but the training sessions address all of those issues and more.
  • I wish there were more focused formatting tools. At this point, I don't know how to change the text color or format my output beyond the legacy defaults I inherited when I started this job. My fellow writers and I still sometimes struggle with putting things where we want them to go simply because they aren't the right field type at that location.
Before I took the intermediate training, I was so frustrated with Paligo that I mentioned it negatively in a networking event. Now that I have taken the training, I will be correcting that comment at the next one. :)
However, part of what I inherited was a badly managed library, and I am working hard with my fellow writers to restructure and re-present the content. I have only been working with Paligo for a month and a half, and while it's been a struggle to get here, I'm glad I learned it so that I can truly utilize its content reuse strengths across three different product lines.
It probably would not be ideal for desktop layout or on-demand production environments.
The training is exceptional, and follow-up support is absolutely comprehensive. The main minds behind this company are dedicated to its success, and you can tell by how responsive they are to their customers.

I almost feel as if I have a professional connection with my main contact for this company, and it makes me confident that any time I reach out, there will always be a supportive answer following. This is an excellent aspect for ANY company, and Paligo has it in spades. Thank you, Mike.
Paul LaBarbera | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We're using Paligo to manage the documentation libraries for several products. After a merger, we needed to consolidate documentation into a single platform and workflow. We were previously authoring in Zendesk and Confluence. Paligo has many benefits: A topic-based XML authoring tool provides flexibility with your content. While there is extra work involved compared to authoring a random Zendesk article, this flexibility lets my team adapt to a changing industry quickly. We're no longer locked into a single platform that we push our content into.
  • Once you get the hang of it, the workflow and UX lets you build highly structured content relatively quickly.
  • The number of publishing options is outstanding.
  • If you're disciplined, you can maintain a giant documentation library that is very well organized. Content re-use can be done at an enterprise-wide level.
  • The SaaS platform occasionally hiccups on us. This has never resulted in lost content, but we'll occasionally get "Cannot connect to server errors". Admittedly, this hasn't happened much at all lately.
  • The Zendesk publication feature is great (no author Help Authoring Tool has it built in), but the feature set could be expanded.
Paligo is not appropriate if you are not interested in structured authoring. If you do not value having your content in extensible XML formats, then the value of Paligo is limited (but your customers will notice the lazy attitude in your writing style). If you really value the content you're producing, you should be using an XML-based authoring tool. Paligo is best in class.
Sarah Holdgrafer | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
Currently, only my team uses Paligo. My team creates end-user help articles through ZenDesk Guide. Paligo is a CCMS that allows us to use structured authoring to manage all our content and publish not just to ZenDesk, but to PDF and HTML5 as well.

Paligo allows us to single source the majority of our end-user content, reuse topics across multiple articles, publish to multiple channels, filter for languages and markets by country, manage content in an intuitive way, and remove all styling concerns from the content creation process so we can focus just on writing the content and managing article images and gifs. Our article styles are handled all through our external CSS, which automatically applies to articles when we publish to Zendesk. This makes our content creation process shorter overall and allows us to reuse content in multiple formats with different styling, without creating the content from scratch each time.

In addition to managing our knowledge base content, we've also created feature-level user guides in PDF to distribute to select users, and PDF guides to send to developer partners as product documentation required for the plugin development approval process.
  • Topic reuse - many of our tutorial and how-to articles include procedures with the same first steps. Reuse allows us to create these steps once, including images, and reuse them in as many articles as we need.
  • Single sourcing - At any time if the text or images in reused topics need updating, we just update the original topic and the changes reflect in every article that uses that topic.
  • Content management - the topic and media management is excellent. we can organize however we need, rename topics and images as needed and move them around within the folder structure without breaking any links to the topics / articles they are used in (each topic and asset has a unique ID number that doesn't change, allow us to rename and move assets to best suit our needs)
  • Filtering and variables - we can create a single topic that includes all the information for different markets (in this case, different content for accounts in different countries) and by using filtering and variables when building the content and in the publishing workflow I can publish just the US content to our US help center, the UK content to the UK help center, and the Australian content to the Australia help center, but using manage a single article within Paligo itself.
  • Translation and localization workflow - the translation workflow (sending topics to be translated into another language) and localization workflow (publishing the same content in multiple languages) works well within the ZenDesk integration. It uses the ZenDesk localization settings to ensure the proper translation ends up in the correct articlein Zendesk.
  • Speed - since it is cloud-based we do sometimes run into speed issues in loading or saving content
  • steep learning curve requiring training - the Paligo trainer is great, and their help center is also very good, but for individuals not already well versed in structured authoring it's a bit of an uphill battle to really understand why the UI works the way it does. that said, their support is incredibly helpful and enthusiastic!
  • Stats - it would be great to have easier access to data showing which users on my team have created what content and performed what actions within the app or on specific content. This is mostly a manager need as I need to report progress to my manager regularly.
A recommendation would be dependent on their needs and numerous other factors, including their publishing channels. For my situation, where a good chunk of content (especially images) are used across dozens of articles, we're documenting the use of an entire SaaS platform and the 100+ integrations we have, and we publish different versions of some content based on account country, it's an ideal fit. Any help center that has more than 100 articles hosted on ZenDesk could potentially benefit from switching to a cloud-based CCMS.

Structured authoring is less appropriate for managing content that is constantly changing or doesn't have a unified structure, like blogs, for instance.
The support is quick, the team very knowledgeable and invested in my success. The only reason I didn't give it a 10 is because there is no chat support (yet). But, so far, the responses have been quick enough that hasn't been an issue.