Contentful vs Paligo

• Contentful provides organized, flexible data models with support for a variety of data types and content editors (e.g. WYSIWYGs, form fields, raw text areas).
• Contentful has great built-in versioning features with history and draft states so it's easy to make updates and revert when needed.
• Contentful has an intuitive user interface and good support for multiple spaces (which can be helpful for companies that need separate projects for dev/staging/production).

Read full review

• Topic reuse - many of our tutorial and how-to articles include procedures with the same first steps. Reuse allows us to create these steps once, including images, and reuse them in as many articles as we need.
• Single sourcing - At any time if the text or images in reused topics need updating, we just update the original topic and the changes reflect in every article that uses that topic.
• Content management - the topic and media management is excellent. we can organize however we need, rename topics and images as needed and move them around within the folder structure without breaking any links to the topics / articles they are used in (each topic and asset has a unique ID number that doesn't change, allow us to rename and move assets to best suit our needs)
• Filtering and variables - we can create a single topic that includes all the information for different markets (in this case, different content for accounts in different countries) and by using filtering and variables when building the content and in the publishing workflow I can publish just the US content to our US help center, the UK content to the UK help center, and the Australian content to the Australia help center, but using manage a single article within Paligo itself.
• Translation and localization workflow - the translation workflow (sending topics to be translated into another language) and localization workflow (publishing the same content in multiple languages) works well within the ZenDesk integration. It uses the ZenDesk localization settings to ensure the proper translation ends up in the correct articlein Zendesk.

Read full review

• Preview of changes prior to publishing
• The ability to use a spell check plug-in when working on content (it doesn't work well with Grammarly)

Read full review

• The SaaS platform occasionally hiccups on us. This has never resulted in lost content, but we'll occasionally get "Cannot connect to server errors". Admittedly, this hasn't happened much at all lately.
• The ZenDesk publication feature is great (no author Help Authoring Tool has it built in), but the feature set could be expanded.

Read full review

• It speed up our content creation process
• We've freed up dev and design resources for more important projects
• Given freedom to people to create new pages, while keeping some control so they wouldn't make serious mistakes

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