Paligo vs. Confluence
107 views
Skip to first unread message
Robert Lauriston
Aug 10, 2016, 4:28:54 PM8/10/16
to paligo_tw
Random thoughts as I get up to speed in Paligo:
One big plus for Paligo: it has a canonical way to do all the things that were kind of kludgy in Confluence. For example, I can define conditional text for output using attributes such as audience and condition.
The editor takes some getting used to, but I don't see how that can be helped when you're using a structured source format.
Having a single source of support is great.
It was weird at first that some features (such as adding fonts) are inaccessible, but I just ask them for what we need and they do it quickly, which is easy to get used to.
Paligo has already fixed most of the bugs I've reported. I've been reporting bugs to Atlassian for over five years and most are still open. Obviously it helps that Paligo's business is technical documentation tools while for Atlassian that's just a minor market for a non-flagship product. K15t was much better about fixing bugs than Atlassian was.
One big plus for Paligo: it has a canonical way to do all the things that were kind of kludgy in Confluence. For example, I can define conditional text for output using attributes such as audience and condition.
The editor takes some getting used to, but I don't see how that can be helped when you're using a structured source format.
Having a single source of support is great.
It was weird at first that some features (such as adding fonts) are inaccessible, but I just ask them for what we need and they do it quickly, which is easy to get used to.
Paligo has already fixed most of the bugs I've reported. I've been reporting bugs to Atlassian for over five years and most are still open. Obviously it helps that Paligo's business is technical documentation tools while for Atlassian that's just a minor market for a non-flagship product. K15t was much better about fixing bugs than Atlassian was.
Reply all
Reply to author
Forward
0 new messages