Contentful vs Drupal

• 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

• Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
• Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
• Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.

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

• Drupal's admin side is very powerful and flexible, but it's a little bit harder to wrap one's mind around. If a customer is familiar with using a basic WordPress site, showing them the full Drupal back-end might be overwhelming and confusing at first. Luckily you can easily limit and customize the admin pages that each role sees.
• Drupal is huge and complex. Doing simple things is generally simple, but more advanced capabilities of Drupal have a higher learning curve (as can be expected). You can build a Drupal site quickly, but don't expect to build your dream site with loads of custom features in a week.
• Ready-made themes are more sparse than something like WordPress. If you're most interested in simply plugging an existing theme in and using it, you won't find as many professional-looking themes out of the box. There are some, but with Drupal, the best results are usually achieved by finding a good base theme and creating your own child theme based off of it.

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

• Our overall site traffic has grown exponentially since we have moved to it.
• We have been able to bring a standardized format to all of our resources and communications.
• Promoting new products is much easier due to the easy to use interface of Drupal, we can get a new product launch page up in record time compared to our old platform.

Read full review