Confluence is a collaboration and content sharing platform used primarily by customers who are already using Atlassian's Jira project tracking product. The product appeals particularly to IT users.
$10
per month
Paligo
Score 9.8 out of 10
N/A
Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.
We were using our own, custom management scheme - relying on tools like SharePoint to store and collaboratively edit. But we were lacking the reusability feature and content control features that Paligo provides.
Compared to Author-It, Paligo is a godsend. It's so much more performant, the output quality is much higher, and the user experience is unmatched. Before we switched to Paligo, I had to spend multiple working days just fixing the broken output that Author-It has given me, …
It has a comment option on the page, where you can tag other teammates tagging them. it sends the mail notification. Comment at the page end is pretty good for referring to other stakeholders and future references of the topic on the page. Creating the highlights of the discussions, and meeting held points with highlighted tagging. Easy shortcuts such as to add a date just type "//". The interface is cool and has easy shortcuts for quick page making.
Paligo is particularly well suited for developing similar document sets for multiple products or product lines. It is not a page layout application, so don't expect the same capabilities as popular applications for graphics-heavy documentation. With some up-front time developing good layouts, however, Paligo does manage to create very usable PDF output for customer-facing documents.
The review mode is super convenient. Comparing a snapshot of the previous versions with the current one clearly outlines the respective changes and reduces the necessary content to review tremendously.
The option to reuse text fragments is another handy feature. Text fragments will be updated whenever the original text fragment is altered is also extremely helpful.
Managing a content's structure was never easier. An intuitive drag & drop functionality allows you to design your document's structure however you like.
You can also fork content, in addition to reuse text fragments. This is another helpful option that no longer requires you to create repetetive chapters over and over.
Navigation. Similar to other Atlassian products, users have complained that aspects of Confluence are difficult to learn right away[.]
An issue that users can face when using Confluence is attempting to edit a document while someone else is editing. Although users can access the document and save it, they are unable to see the changes happening in [real-time] that other users are implementing until they refresh their page. Some users have also noted that this can result in loss of edits.
Another drawback of using Confluence is its specific organizational structure. All information is stored within one page or project, although the page is able to be broken up into sections, some users do not prefer this style. Users can use the ‘page tree’ on each page to organize the different elements of each project.
The amount of CSS/JS required to customize a site's appearance can be cumbersome
Product documentation can be lacking, specifically with integrations; in some cases, support offered no real help when trying to solve a problem with an integrated service
Some features require extensive development experience to use, which can sometimes be an obstacle to less-experienced team members
I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.
Confluence can - and in my personal opinion, it will - be a bit hard to use in the first moment. Atlassian is a great company and is eager to help you with any question you have, though. The interface seems to be a bit clumsy at first but the customization options are enough to make it easier and simpler. In general, Confluence is easy to use when you understand what each section does, but this can take a while.
Generally, I'm very happy with Paligo and the productivity gains that I get from using it. There are a few arbitrary limitations on structure, and when applying conditional formatting, that I don't really understand. Unlinking / editing reused text uses this broadly inscrutible colour-coding that I just hate. It would be nice to double-click a component, make edits, then respond to a popup asking if I want to confirm the edit for all linked content, or unlink this instance. Likewise converting from an informal topic insertion to duplicates of its raw contents.
Pages load very quickly, which makes it useful for quickly obtaining information. The search functionality is also very quick and is able to parse through all of the documents to provide the most relevant results for the query. Other information based software gets bogged down, but so far Atlassian Confluence maintains its performance.
This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.
All the support requests I've submitted have been resolved in one way or another. Sometimes it takes some back and forth, which is to be expected. This is where being on a different continent becomes a drawback. Since we became Enterprise users, we've also had an additional level of help and support from a dedicated account manager in the US, and the resolutions seem to come more quickly
We used to use Google Drive to store all of our documentation, but it is disconnected from our every day working environment and it was easy to lose documents and become disorganized within the broad drive environment. [Atlassian] Confluence has kept us more organized and its tight coupling with Jira has made documents more accessible and more likely to be kept up to date.
We moved from Flare to Paligo. One of the main reasons was the fact that Paligo is a cloud product. Collaboration with anyone outside of our team was more difficult with Flare. Also, maintaining a server for Flare content was going to become an issue, and overall I felt the Flare desktop product was prone to errors and issues. The flexibility of assigning Paligo licenses was a huge factor, as was the stability of the cloud platform.
We've gone from folders and folders of Word documents and PDFs into a single system with a search feature to bring all of our data together and trackable
While onboarding took a bit longer for the company (to switch from a Word document centric mindset - to a web-based one), overall the company has embraced the features and power of Confluence within the working stack
However, as costs continue to climb for the Atlassian product, we are forced to continue our evaluation of the product - with replacing it a remote possibility if it begins to outprice its usefulness to us.
I am not involved in the financial decisions for my company regarding Paligo; the decision to migrate our content to this environment predates my hiring. However, I know that the migration effort from WordPress to Paligo was an initially heavy lift, but any content migration effort would be. I believe that ultimately, getting our content out of WordPress was a positive move, and I look forward to seeing what Paligo will help us accomplish in the future. Sorry, no hard numbers from me. :)