Contentful vs. Netlify Platform

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

Netlify is a static website host, so it obviously wouldn't work for hosting dynamic websites built in PHP, such as WordPress or Drupal. It works very well with static sites with a git codebase on something like GitHub. It has automatic deployments, which include preview websites. It works very well with this workflow. There are solutions for allowing content authoring on static websites on Netlify, but I would probably reach for something like WordPress or Drupal for that.

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

• I can connect Github/Gitlab repos or drag and drop code folders directly to host them onto the platform, and can customize build and publish details. It handles all granular details itself, so I don't have to worry about configuring everything like I would have to do on an IaaS like AWS
• Netlify Platform has inbuilt scalability support - meaning automatic upgrading of servers to handle traffic, without us needing to do anything at all, again, unlike IaaS, where we'd have to manually configure scaling
• It has a built in CDN, meaning static applications can be served blazing fast over the web without worrying about traffic or latency

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

• it is not aimed at it but first party laravel support would be nice.
• their free tier was so handy, i wish they start some similar efforts
• incorporate more WebOps mindset

Incentivized

We interact with the CLI via our CI/CD pipeline. It was very straightforward to get set up, and their documentation is thorough. There are a ton of examples online of various setups. We needed to deploy a React SPA, so we required redirects, which was straightforward with Netlify.

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

Netlify Platform is the first choice that we are using in this organization continuously and it's been a very promising platform to use. It also maintains the things very well. it also giving a very good updates. It is very easy to use and very easy to learn. overall it is good.

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

• it's free to get started and to work on small frontend projects for testing and qa
• very nice DNS Management
• quick and easy to use, reduces dev efforts

Incentivized