Paligo does what it says it can do and more.
Content management to develop, and publish regulatory compliance documentation. Addresses the turn-around time needed to publish …
Overview
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.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
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?
- Setup fee optional
For the latest information on pricing, visithttps://paligo.net/pricing
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
47 people also want pricing
Alternatives Pricing
What is MadCap Flare?
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 Ibexa DXP?
Ibexa, headquartered in Oslo, helps B2B companies to stay relevant and succeed by transforming traditional sales strategies into frictionless buying experiences, with their eponymous digial experience platform (DXP).
Product Details
- About
- Integrations
- Competitors
- Tech Details
- Downloadables
- FAQs
What is Paligo?
Paligo is an enterprise-grade cloud-based Component Content Management System (CCMS) with single-sourcing content reuse for technical documentation, training content, policies and procedures, and knowledge management. Paligo is 100% XML in the back end, based on a modified version of DocBook - an established open standard developed for technical documentation. This is to provide future-proofing as well as extensibility and transformability for any current and future applications. The strict structure of XML and solid validation it provides offers possibilities and a consistency that, according to Paligo, no other format can provide.
Companies seek to make their documentation more efficient through single-sourcing and reuse. But many single-sourcing projects fail due to the steep learning curves and costs of implementation of traditional systems. So cloud-based solutions like Paligo aim to enable greater collaboration and efficiency. Using modern web technology reduces the costs of implementation, to increase usability and thereby user acceptance. A cloud-based authoring and publishing platform to reuse and single-source documentation with a clear focus on usability and user acceptance can improve the chance of realizing the return of investment and actually achieving the increase in efficiency.
In an information-enabled world, content is required to help solve problems and guide decision-making. Siloed content creation and management technology have led to content duplication, inconsistent content, and challenges finding the right content for customer and employee experiences. A component content management system (CCMS) like Paligo aims to change that.
Paligo's top features at a glance:
- Structured Authoring
Structured authoring helps make content consistent, accurate, and future-proof. The XML editor enables content reuse, making structured authoring easier.
- Content Reuse
Reuse content at scale with topic-based authoring and smart single sourcing features such as component reuse, block content reuse, the Paligo text fragment reuse, dynamic variables, and conditional content.
- Multi-Channel Publishing
Paligo takes multi-channel publishing to another level. Publish to HTML5, PDF print, SCORM eLearning, Zendesk, Salesforce, GitHub, BitBucket, Amazon S3, and much more.
- Versioning
Paligo features version history and roll-back, version branching, and release management made specifically for technical writers and content authors.
- Translation Management
Paligo Features
- Supported: Single sourcing
- Supported: Content reuse
- Supported: Multi-channel publishing
- Supported: Translation management
- Supported: Contributor editor
- Supported: Structured authoring
- Supported: Topic based authoring
- Supported: Versioning
- Supported: Branching
- Supported: Assignment planner
- Supported: REST API
- Supported: Variables
- Supported: Conditional content
- Supported: CCMS
- Supported: Integrations
- Supported: XML editor
- Supported: Docbook
Paligo Screenshots
Paligo Videos
A quick, high-level look inside Paligo.
An in-depth look at the best-in-class Paligo <> Zendesk integration.
Paligo Integrations
- Zoomin
- Slack
- GitHub
- GitLab
- Microsoft Teams
- Phrase Localization Platform
- Freshdesk
- Crowdin
- Bitbucket
- Algolia
- Amazon S3 (Simple Storage Service)
- Microsoft Azure
- Elastic Enterprise Search
- Oxygen XML Editor
- Google Analytics
- Disqus
- Google Tag Manager
- Mixpanel
- Intercom
- MathType
- Salesforce Service Cloud
- ServiceNow Customer Service Management
- Netlify CMS
- LinkApi, by Semantix
- Zendesk Suite
- Fluid Topics
- DeltaXML Compare and Merge Tools
Paligo Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
| Supported Countries | Global |
| Supported Languages | English |
Paligo Downloadables
Frequently Asked Questions
Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.
Reviewers rate Support Rating highest, with a score of 8.5.
The most common users of Paligo are from Mid-sized Companies (51-1,000 employees).
Comparisons
Compare with
Reviews and Ratings
(34)Attribute Ratings
Reviews
(1-4 of 4)Companies can't remove reviews or game the system. Here's why
September 26, 2023
Paligo does what it says it can do and more.
Content management to develop, and publish regulatory compliance documentation. Addresses the turn-around time needed to publish documentation to provide to the customers. Needed the ability to reuse content, a method to organize content, and an easy method to have content reviewed.
- Ability to re-use content.
- Ability to filter content to specific needs.
- Ability to tag content using variables.
- Better table functionality.
- Move variable table buttons to prevent scrolling to add new variables.
- Ability to locate profiles when a change is needed.
- Re-use content.
- Filtering (profiling).
- Easily publish manuals in multiple formats.
- Reduced time in publishing content and number of personnel needed.
- Excellent collaboration when SMEs need to provide content, review, and approve documentation.
- Easily managed by one person while allowing multiple users access to perform their job tasks.
25
Client support, content development, and content management.
1
Knowledge of Paligo functionality, user needs, and expectations.
- Extensive amount of content.
- Need for content management.
- Ability to allow users access to review, leave comments.
- Created public awareness brochures.
- Develop content for documentation websites.
No
- Cloud Solutions
- Scalability
- Ease of Use
I wouldn't think so.
- Don't know
Change management was a big part of the implementation and was well-handled
- None that I'm aware of
Unsure
Yes
My customer success manager (Alex Jahr) has been phenomenal, accessible, thorough, and responsive.
- Setting up the document structure
- Importing documents
- Publishing documents
- Knowing when to use a variable versus filtering (profiling)
- Finding previously used profiling
Score 10 out of 10
Vetted Review
Verified User
We use Paligo to create and publish our Technical Documentation for all of our products. This includes single-sourcing of content through different products, for multiple audiences and includes translation into multiple languages (both LFT and RTL). We mainly publish PDFs but will be publishing HTML5 content in the future.
- Image insertion, updates and multi-image options for localization
- Single-source content reuse - one piece of content, whether a sentence or a complete topic, can be re-used anywhere else.
- Multiple publication channels and outputs - PDF, HTML, ZenDesk etc.
- Translation auto-translate, plus import and export XLIFF file options makes localization quick and simple.
- Very intuitive UI
- Would appreciate greater ability to set PDF Properties within Paligo.
- Text Callouts for graphics - while Paligo has a few image options, there is no ability to add text callouts to an image that link to related sentences, sections or topics. That would be a huge gamechanger.
- It would be nice to have a more WSIWYG GUI for the Layout section. In can be tricky remembering which components are changed where.
- Positive - we now produce more professional documentation
- Positive - we can rapidly publish new versions of our docs for multiple audiences.
- Positive - Our translation ability is much quicker, and we can easily add new languages with no extra formatting overhead.
They are both good documentation options, but the cloud-native capabilities and intuitive UI of Paligo, plus it's ability to produce excellent output for both PDF and HTML5 were the main reasons I chose Paligo. I am very satisfied with my choice.
No. It has not been necessary because I always receive a response within a few hours.
No
I needed a special footer into into a document, that did not appear to be possible from the Paligo help.
I emailed support, they did their research and found a solution for me with a couple of days that I have been using ever since.
I emailed support, they did their research and found a solution for me with a couple of days that I have been using ever since.
May 21, 2019
Steep Learning Curve, Worth The Effort
Score 8 out of 10
Vetted Review
Verified User
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 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.
- 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. :)
5
Technical Writers: there are three of us. We send publications for review to several SMEs who provide feedback; the review function is actually quite elegant. We integrate that feedback into the content we ultimately publish.
Our manager and our VP are also contributors, but aren't involved with Paligo as frequently as we.
Our manager and our VP are also contributors, but aren't involved with Paligo as frequently as we.
Yes
It absolutely was. Mike responded with a detailed response of how the issue happened and why it was acting the way it was; user error on our part (not uncommon; we're both still new to the product). It was both a learning moment and a great customer service experience that I deeply appreciate on a professional level. (We've all got deadlines...thanks, Mike!)
My coworker and I are still new to this company and this product, and my coworker had managed to blitz up a topic so completely that it looked drastically different live than in Preview. We were worried about how it was going to publish, so I sent the issue to Paligo Support.
Not only did Mike fix the file for us, but he also explained, in granular detail, each of the specific issues that we had created with hacking away in the product with what I've come to call "Word Brain." It really brought to light the different aspects of the software that we weren't utilizing properly, and another user error became a learning moment.
Not only did Mike fix the file for us, but he also explained, in granular detail, each of the specific issues that we had created with hacking away in the product with what I've come to call "Word Brain." It really brought to light the different aspects of the software that we weren't utilizing properly, and another user error became a learning moment.
- Content reuse
- Keyboard shortcuts
- Cross-referencing
- Publication variety
- Text formatting (color/spacing/font)
- Output template formatting
- Initial learning curve of the software
November 29, 2018
Paligo is a great CCMS and structured authoring tool!
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.
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.
- Positive - has allowed us to create templates for integration documentation. this has greatly sped up our process for creating articles for each of our integrations, which we haven't had up to this point.
- Positive - has created greater alignment between the self-service content team and the marketing team.
- Positive - has introduced a review and feedback workflow for our content creation that was not available in ZenDesk. The feedback directly in the app allows me to pinpoint comments about text and other elements so my writers can address them directly and become better writers in the long term.
- Negative - long ramp up time due to a completely different approach to creating content. My team was training in early August and we have not yet published our new help center (though, to be fair, it is a lot of content that had to be completely rewritten)
- Positive - any UI updates only require updating a single image, which has saved us dozens of hours of updating already.
I trialed a version of Oxygen XML editor, but the fact that Paligo is cloud-based and integrates directly to Zendesk sold me, even though Oxygen XML is essentially the de facto standard for most structured authoring.
Content Author / Administrator
100-1,000 pages
No
Support is included in my subscription level (business plan)
Yes
yes, the issue was resolved within 24 hours
During the early days when I was still learning about the publication process for multilanguage, Steve (my account manager) was incredibly patient while I tested a number of scenarios with Paligo and ZenDesk and explained in great detail why things were working in a way I wasn't expecting. It was a major realignment in my thinking of how the workflow was meant to function. It turns my particular use case was a bit unusual and I worked with Paligo closely to customize the publishing workflow to accomplish what I needed.