Contentful is a cloud based CMS solution that provides the ability to manage content across multiple platforms.The editing interface allows for managing content interactively and provides developers the ability to deliver the content with the programming language and template framework of their choice.
$489
eZ Platform
Score 5.0 out of 10
N/A
ezPlatform, formerly ezPublish is a content management solution from eZ Systems. The vendor says their solution provides organizations with the technology and framework to build a suite of digital experiences including news and media sites, brand sites, multichannel apps and the Internet of Things, intranets and web portals. This solution is multichannel, multilingual and multisite ready.
ezPlatform features user defined content and classes, version control, templates, workflow…
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 )
For a new site: 1. Are there any hosting requirements? eZ Publish works best on a traditional LAMP stack. 2. What is the expertise of the development and systems administrations individuals? There should be some PHP development experience and a solid level of Apache and MySQL hosting. 3. Who will be managing the content of the site? What is their bandwidth for training? For ongoing content changes?
Content Taxonomy: Content is managed in a tree. Though taxonomy vs folksonomy is a near-religious debate among professionals, clients seeing the system for the first time just seem to "get it" more often.
Content Flexibility: Common content types such as blog posts and articles are available out of the box. However, customizing these and creating new content types is very easy.
Developer Friendly: Developers need only a little PHP experience to get started. Of course being an expert doesn't hurt and opens the door for the development of custom modules.
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.
The template language: Outputting content or doing something special with it requires use of the templating language. Myself along with other developers I have trained, found this to be one of the biggest hurdles.
Layout of physical files: The system decides what settings files and templates to use based on a hierarchy of modules. The same file can exist in multiple modules and you can find yourself deep within very similar looking folder structures, causing confusion during debugging.
Community: eZ has a solid set of community contributors but the gap between it and Drupal or Wordpress is pretty large.
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.
eZ Publish isn't as large in community size and number of installations as other content management systems. However, it's just as capable and met our needs:
Developers, system administrators, and project manager can all speak the same language during the development and maintenance cycles of a site.
End-user training is very straight-forward.
Vendor support is available.
Client IT departments can access if need (developers/designers/sysadmins).
The community is there (forums) and there are solid contributions (extensions) from both the vendor and the community.
Common knowledge: By making eZ a core offering, developers, system administrators, and project managers were able to communicate with each other effectively.
Training: Due to its content taxonomy, end-user training often went well.
Support: In our case, we had Gold support from eZ Publish which saved time and helped with customizations.
