Contentful vs Plone

• 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

• Plone is a folder-based system, organising content in a similar way desktop-users are doing for the last two decades. No need to teach non-tech customers some relational-database like paradigm for content management.
• Plone is secure. It is the most secure CMS you can get your hands on.
• Plone is flexible, and makes fast development 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

• Not everything is configurable or editable by Plone, and when you need to adjust or add custom pieces in, you need to deal with Zope. Zope has an ugly, confusing and difficult UI and structure as a backend.
• Using 3rd party products is difficult to do - there are a few different ways to get them installed, all of which take a bit of luck to get right.
• Building custom products for Plone is not fun. You've got to deal with an archaic framework to tie in that is not well documented (there is documentation about many things, but not great documentation and there are a lot of holes in the documentation).

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

• Before Plone there were couple of dozens of web editors. Now it is in the hundreds. That leads to more information on the websites and more accuracy.
• Through the good SEO properties of Plone, our content is more easily found on Google compared to some of our competitors.
• Plone being an Open Source product there hasn't been any license payments for a decade.

Read full review