Contentful vs React

• Contentful provides organized, flexible data models with support for a variety of data types and content editors (e.g. WYSIWYGs, form fields, raw text areas).
• Contentful has great built-in versioning features with history and draft states so it's easy to make updates and revert when needed.
• Contentful has an intuitive user interface and good support for multiple spaces (which can be helpful for companies that need separate projects for dev/staging/production).

Read full review

• React is designed around the notion of generated html as opposed to templated html. This provides more flexibility in building elements on a page, and allows developers to create html that is programmatically configured based on runtime considerations.
• React uses JSX, which is HTML templating integrated into javascript code. This simplifies the generation of complex structures, especially those that vary based on runtime and interactive data.
• React is more efficient because it generates a virtual DOM rather than directly building in in the actual DOM. By building 'offline' in this manner, the DOM generation is faster. After building, it can be installed in one operation.
• React only builds those portions of the display that have changed, making display updates more efficient.

Read full review

• Preview of changes prior to publishing
• The ability to use a spell check plug-in when working on content (it doesn't work well with Grammarly)

Read full review

• React could get very frustrating unless you start thinking in React. React enforces a top down hierarchy of data flow and offers no way for the data to communicate backwards. This is a big shift in mindset coming from Angular 1.x. This constraint is really a big factor that determines how to organize your code and how you might want to write your own Components.
• Because of the self imposed top down hierarchy, you end up having a heavy parents with dumb children. Because parents would need to the bulk of the work, they usually manage the state, while passing callbacks to the child components. If not properly designed, this could lead to the callback hell, where you could have callbacks passing through like multiple children.
• As with any library, you will have to iterate through multiple designs to come up with a ways to avoid "heavy parent components" in React. One obvious solution is using some open source tools like Redux, but we opted for a variation of it to suit our needs.

Read full review

• It speed up our content creation process
• We've freed up dev and design resources for more important projects
• Given freedom to people to create new pages, while keeping some control so they wouldn't make serious mistakes

Read full review

• React sped up the time to implement new features, providing much better code-reuse across the team
• React's excellent performance made it so new components ran faster in the browser
• Since React is so popular, it's been easy to recruit new developers to the team who already have a familiarity with the library

Read full review