React

A headless CMS does not come with a web interface where readers will see published content. Instead, a headless system acts more like a database: it hosts content, and your app uses an API to fetch content to display. As a result, your choice of app architecture is not tied to your choice of CMS. This can be especially helpful if you want to incorporate managed content into an app that is not primarily a publishing platform, or if you want to present the same content differently in different contexts as was the case with our web vs mobile apps.

This recipe is part of the Flow Cookbook series. Flow and React are both Facebook projects - so as you might imagine, they work quite well together. React components can take type parameters to specify types for props and state. Type-checking works well with both functional and class components. Flow type annotations provide an alternative to propTypes runtime checks. Flow’s static checking has some advantages: Problems are reported immediately - it is not necessary to run tests that evaluate every component to identify props mismatches. Flow types can be more precise and concise than propTypes. Flow can also check state as well as props. In addition to checking that a component gets the correct props, Flow checks that props and states are used correctly within the component’s render method, and in other component methods. …