With our last documentation tool, it was necessary to …
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
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!
Entry-level set up fee?
- Setup fee optional
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
- Tech Details
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.
Paligo features version history and roll-back, version branching, and release management made specifically for technical writers and content authors.
- Translation Management
- 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
- Microsoft Teams
- Amazon S3 (Simple Storage Service)
- Microsoft Azure
- Elastic Enterprise Search, with Site Search
- Oxygen XML Editor
- Google Analytics
- Google Tag Manager
- Fluid Topics
- Delta XML
- MadCap Flare
- Adobe Technical Communication Suite
|Deployment Types||Software as a Service (SaaS), Cloud, or Web-Based|
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.
Structured authoring is less appropriate for managing content that is constantly changing or doesn't have a unified structure, like blogs, for instance.
- 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.