Paligo

“powerful cloud documentation workflow”

Pros

Compared with many other top documentation platforms, this software being cloud-based is a huge advantage because my PMs can review my updates without any hassle. The localization setup is thoughtfully built and the translation feature works really well. the overall documentation workflow feels clearly designed with technical writers in mind, with variables that are simple to create and cross-referencing that's painless to manage.

Cons

One thing I'd still want is more control over where the copyright page can be placed. The initial training course wasn't very useful and the weekly help-hour happened at a time that didn't work well for me. Even so, the platform is adaptive enough that I learned the basics right away and its support team is very fast when I reach out with more advanced questions. The user community is also excellent...special thanks to Rochelle for replying to a few questions I posted there.

“Amazing tool”

Pros

I love how simple content reuse is. The document structure panel makes it very practical to pull in existing topics and move them around as needed. Branching is also really valuable because it lets us work on multiple versions of the same document at the same time. Among its many capabilities, the ones that help our team most are text variables, filters for including or excluding content across different document versions and the localization features especially the translation editor and support for localized images.

Cons

There are a few downsides i'd like to mention. A confirmed translation does not automatically switch back to unconfirmed when the source text is updated so changes can be missed and translators may not realize a revision is necessary. Another issue comes up during translation.. the right-click menu shows which tags or inline elements can be pulled from the source but if you type directly in the translation dialog and insert an inline image that way, the image does not keep its original size. To avoid that, you have to use the copy source text option, paste everything into the translation editor and then handle the inline elements step by step which becomes particularly tedious for RTL languages. It also sometimes becomes unavailable for stretches ranging from a few minutes to as long as half an hour and that is quite frustrating.

“frustrating editor”

Pros

Something I can say in its favor is that customer support responds fairly quickly.

Cons

Nothing about the product really works for me. From the strong text editor to the weak feature explanations and scattered onboarding, the whole experience is frustrating. It feels like the platform puts feature depth ahead of actual usability. Managing modular content may sound appealing on paper but in practice it becomes tiring because the system is so stiff and hard to work with. A good example is the preview function which only lets you look at topics one at a time so you never get a complete view of the document until after it has been published. Customizing CSS and JavaScript is another big pain point. It ends up consuming far too much developer time just to make styling changes even though this seems like an area where better options for non-technical users could exist. Instead, you have to dig through messy bootstrap folders to handle even basic edits. Translation workflows are unnecessarily awkward too since you constantly have to work around the system just to keep document statuses correct. You Cant update a status directly from the topic itself...you have to go to the folder where it lives, change it there and then return to the translation or editing screen. ALsoo, the documentation is surprisingly poor for a technical writing and authoring platform. Most of it explains what features are but doesn't really show how to use them well. Overall the software feels like it was built with the expectation that users will either figure everything out by themselves or already know the underlying doc-book concepts. A modern-looking interface on top of confusing and unfriendly functionality does not make this a good product. I would much rather see fewer features that are implemented well than a huge set of capabilities that are executed badly.