2. Push to Bitbucket for HTML5 embedded.
3. Push to Zendesk.
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?
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. The vendor states cloud-based solutions like Paligo enable greater collaboration, efficiency and profitability. Using modern web technology reduces the costs of implementation, and increases 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.
Implementing an intelligent content strategy using a component content management system (CCMS) like Paligo can 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
- MadCap Flare
- Adobe Technical Communication Suite
- 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.
- Paligo allowed us to pivot our docs strategy and recreate our entire docs set (approx. 60k words) in a couple of months
- Our users have complimented us on the ease of use and structure of our output
- Enabled real-time updates for documentation.
- Enabled true structure for our documentation.
- Before we had Paligo, we didn't have a professional tool. We were using Google docs and creating ugly PDFs that took days to manipulate. Paligo lets us publish to multiple formats and integrated platforms in minutes, with professional results.
- Paligo's built-in translation features let us deliver translated documents for expos, datasheets, and users with minimal cost and time.
- Paligo lets us work as a team. When one project becomes urgent, the team comes together in a doc sprint and completes the project with everyone contributing. The final deliverables are professional and fast. In short, Paligo enables us to join the Agile teams and deliver on time, with quality.
- 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. :)
- My company is in the process of merging features of two distinct platforms into a single modular platform. The topic-based nature of Paligo's library lets my team stay ahead of the curve. Getting our content into Paligo was a ton of work, but we're in good shape now and this will save us from huge amounts of hassle in the future.
- 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.