Likelihood to Recommend Well suited for our needs of multiple images for auto auctions from a variety of sellers. Pointing them to one platform is easier than attempting to use a variety of platforms as we were doing before (email, slack,
Dropbox and
Google Drive would randomly be used by a variety of employees )
Read full review 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.
Read full review Pros Flexible. This CMS can be easily extended and provide access to dynamic content Simple. The WYSWG is very easy to work with and identifying pages and content in the system is fairly easy Clean Interface. The interface is clean and uncluttered keeping focus on the content and not other factors. Read full review 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. Read full review Cons Contentful uses "references" to allow you to build very modular content. If I have a "slider" content type, I can create a "slide" content type which references a "button" content type, and so forth. This works well, but I occasionally wish there was a better solution for one-off content, like a settings page. Currently, this is done for creating an entire content type called "settings" with a single entry. Not a big deal, but not ideal, either. There are a few quirks with GatsbyJS integration, etc, but these issues are being fixed and improved upon very quickly. A minor gripe, but Contentful does not have a way to organize fields within an entry. Entries with many fields are somewhat tiresome to scroll through. Read full review 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 Read full review Likelihood to Renew Paligo single-sources beautifully. Allows for customization. Has the best translation features. Has the best support services.
Read full review Usability 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.
Read full review Support Rating 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
Read full review Implementation Rating Everything went well
Read full review Alternatives Considered In the past we've used
WordPress to manage documentation content.
WordPress was more flexible than Contentful but also prone to inconsistencies and we ended having a lot of hacks to accomplish various
WordPress tricks. With Contentful there's less ambiguity so content producers are less likely to go astray. We also have our own in-house programmatic template solution for managing content, but this was a previous pain point when we needed to get the dev team to do a deploy for every content change.
Read full review 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.
Read full review Return on Investment Positive - new hires are able to get onboarded quicker with us using Contentful Positive - we can customize the journey of what modules/material the user sees after a course/video/article Positive - it's been an overall game changer when hiring external candidates who need extensive training Read full review 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. :) Read full review ScreenShots