Contentful vs. Craft CMS

Contentful is well suited for folks who want a simple, clean, easy-to-use interface for a JAVASCRIPT website. If you do not want a javascript website you should look [elsewhere].

Incentivized

Suitable for mid-size to large websites (20 pages+). If you have a massive project with dozens or hundreds of content contributors, complex editorial process/workflow, are tied to a non-Linux platform (Microsoft Server), you may want an enterprise CMS like Episerver. If you need a small, cheap, theme-based, basic website with 5-15 pages, you'll probably go to WordPress.

Incentivized

• 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)

Incentivized

• Design-agnostic templating system. No themes. This means you can use whatever HTML, CSS, JS you want, and integrate it with Craft.
• Versatile field types, with 3rd party plugins providing a bunch more. Everything from plain text to address, color picker, date/time, file assets, one-to-many relationships, and more.
• Control panel with clean, responsive UI makes content updates easy for clients.

Incentivized

• 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).

Incentivized

• Could use a more robust implementation of rich text editor.
• Some functionality that requires plugins, for example, advanced field management, should be part of the core install.
• It should be a bit easier to brand the control panel w/logo and color scheme.

Incentivized

Easy to use and much more organized as a single platform versus multi. The layout is clean and easy to read and we don’t have to worry about certain users safe guarding data or content then losing it when they leave the company. It’s a one stop shop for imagery

Incentivized

Craft was originally developed in response to ExpressionEngine's shortcomings. While ExpressionEngine has caught up in some regards, it still looks and feels a bit unpolished by comparison. Additionally, ExpressionEngine's vendor has never gotten UI right - not on their website, nor in their CMS. Craft remains easier to use, more polished and provides a wider feature set in its base install (without needing plugins). As for WordPress - while I recognize its massive popularity, I find its reliance on themes, third-party plugins, along with security shortcomings, make it a poor fit for the larger custom projects we build. On the other hand, if you want to throw up a passable website in a day, you can't beat WordPress.

Incentivized

• There was no negative impact as such.
• Positive impact is increase in sales.
• More work is delivered due to reusability and other features within a time and less manual effort.

Incentivized

• We don't have hard numbers on Craft's impact on our ROI, but we recognize that its feature set, ease of use, and integrated ECommerce allows offering a superior product to clients.

Incentivized