Overall Satisfaction with Paligo
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.
- 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.
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.