What do you like best about Paligo?
The first characteristic of Paligo that most users notice is that it is cloud-based, which allows all users to work from their computer (Mac or PC) and browser of choice. Authors, contributors, and reviewers don't need to install anything to use Paligo, unlike most competing products. This makes Paligo easy to implement. And unlike most cloud-based tools of a similar size, it's surprisingly fast.
As you begin using Paligo, you'll see the real power of it, which is true, complete content reuse. Paligo assigns every element a unique identifier, and you can reference that identifier anywhere. Best of all, you can use the user interface tools to reuse content, which means you don't have to enter the long unique IDs in the DocBook code.
However, if you prefer to see and manipulate the DocBook markup, you can easily do this at any time. I occasionally find that it's easier to copy and paste bits of markup than repeating steps in the UI.
Once you learn your way around Paligo, you will never duplicate efforts.
Next you'll notice that you can customize anything in Paligo. You can customize most common elements in the layout editor. You can customize less common elements through a custom CSS file. And if you want to really change the default layout, you can even create custom JavaScript files.
Versioning documentation is intuitive for anyone who has worked with any standard source control tool.
Administration of Paligo is simple. Managing users is easy and straightforward.
I have imported Word and PDF content into Paligo with good results. The topics only required minimal cleanup.
Paligo customer support is responsive, friendly, and thorough.
I found integrating Paligo with Slack, AWS, and Zendesk to be fast and easy.
I've extensively used four CCMSs over the years, and Paligo is the best at truly reusing content. Review collected by and hosted on G2.com.
What do you dislike about Paligo?
The user interface is a bit inconsistent. For example, when editing a topic, you do not need to click "Save" to save changes (unless you select that option in the settings), but you must click "Save" to save any changes to the table of contents or layout editor.
The layout editor is quite difficult to navigate. It's a sea of drop-down menus. In the short-term, it's begging for a search feature. In the long-term, it needs to be overhauled to be much more intuitive to navigate.
One downside to being 100% cloud-based means that you can't work in Paligo when you're offline, such as when you're on an airplane.
Selecting a variable requires several clicks. Ideally, Paligo would use an auto-complete feature to anticipate which variable you'd like to use in a given situation. Competing products have similar features.
If you've never used DocBook before, there is some ramp-up time to learn its structure. If you've used DITA, but not DocBook, it's an easy transition. They are similar.
Paligo lacks an internal CSS editor. You must make any CSS edits outside of the tool and upload your CSS file through the aforementioned, hard to navigate, layout editor. This becomes an issue when you make frequent CSS edits. What's more, you need to upload a CSS file for each layout. Ideally, you'd be able to edit the CSS file right in Paligo, and rather than uploading it, you could just point to it.
As a young company, I'm sure that Paligo is aware of these drawbacks and has solutions on their roadmap. I suggest that they invest in UX designers to continue to enhance the user interface and workflows. Review collected by and hosted on G2.com.