React can be rendered on in the Browsers DOM, but also on the server using ReactDOMServer, a library that emulates the DOM in the popular Node.js environment. This can be used to improve first load performance, but the process of rendering React is not simple compared to traditional string based templates.
Colocation of GraphQL queries is a growing trend in the world of React driven apps. What this means is that the data fetching GraphQL query is placed in the same location as the component's view logic. This is somewhat of a radical departure from the MVC architecture that many developers have been used to for decades.
Static site generators have been around for a number of years. Since Ruby and Jekyll started the current trend of publishing content as static HTML files, React.js has become a staple for UI developers. Gatsby.js is a versatile static site generator based on React and also uses GraphQL as an internal API.
WordPress has been on the React.js bandwagon for some years now. Since the introduction of the Calypso interface for WordPress.com, the use of React has expanded to it's use in the Gutenberg editor as well. Now with the licensing woes of the BSD+Patents licensing gone the community can keep moving forward with the UI library from Facebook with full steam.
After a number of years of confusion and FUD around it's licensing of React.js, Facebook has stated it will change the license for the popular UI library in the upcoming React 16 release.
Automattic adopted React.js for their commercial WordPress.com shell Calypso in late 2015. Since that time React has become immensely popular and has even been been proposed as being a part of the Open Source WordPress distribution.
GraphQL is a hot topic now going into
GraphQL is the perfect option for sitebuilding using the decoupled CMS pattern. A well defined, easy to use API format is a clear advantage over product specific REST APIs. What are the best options for a GraphQL CMS going into 2018?