Contentful vs Paligo

• Clean, modern interface (not clunky and outdated, like WordPress)
• High degree of flexibility (I can structure data any way my clients need)
• Enables headless frontend (i.e. I can build any frontend I want without having to change my CMS)

Read full review

• The topic/publication structure is quite graceful. It makes setting up an outline of content quite intuitive, and after the tools are identified and defined, it's much simpler to set up a large document and work with others to produce it.
• Strict field definitions and use cases make topic structuring inherent in the workflow, which brings more attention to content handling. The train of thought required to utilize the tool also improves the train of thought required to focus the content, making for a better ultimate publication.
• The output capabilities and Salesforce integration make publishing the files very easy.

Read full review

• The new Contentful "branches" feature looked promising (it appears to mirror a git-like repository) but it requires the CLI, which isn't necessarily practical for teams that aren't current CLI users. It would be nice if the management of this feature were available via the UI (without that it causes more confusion than anything).
• The Contentful data modeling method makes for a bit of an awkward SDK developer experience in some strongly typed languages like Java. Most things that you might need can be accomplished, but it feels like the experience could be smoother.
• It would be nice if there were a way to migrate data between spaces (e.g. from your staging space to production).

Read full review

• Speed - since it is cloud-based we do sometimes run into speed issues in loading or saving content
• steep learning curve requiring training - the Paligo trainer is great, and their help center is also very good, but for individuals not already well versed in structured authoring it's a bit of an uphill battle to really understand why the UI works the way it does. that said, their support is incredibly helpful and enthusiastic!
• Stats - it would be great to have easier access to data showing which users on my team have created what content and performed what actions within the app or on specific content. This is mostly a manager need as I need to report progress to my manager regularly.

Read full review

• Positive: faster changes and new associates can easily navigate without prior training/knowledge of CMS to make content updates
• Negative: Our website manager/provider can keep certain abilities (like changing specific images) so they can charge a fee for making the change

Read full review

• Enabled real-time updates for documentation.
• Enabled true structure for our documentation.

Read full review