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
- 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.
- PDF and HTML layout design
- Batch publishing
- Web based
- Easy to use design
- Automated batch publishing to a local drive
- Pre-made layout templates eg. product flyers or startup guide PDF templates that could be then customized
- A solution to create a complex documentation website based on html publications
- Streamlined authoring and publication workflow
- Content reuse
- User-friendly UI
- No content reuse at the individual phrase level (within paragraphs)
- No GUI theme editor
- 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.
- 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.
- 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.
- 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.
- 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.