Use ReactJS/GraphQL for all CMS interfaces
With the 4.0 release, we've redeveloped the "assets" section in ReactJS, and created a new "campaigns" section on the same foundations. We've previously blogged about why that's a good idea: https://www.silverstripe.org/blog/cutting-through-the-noise-why-silverstripe-4-will-use-reactjs/
Major sections like "pages" or "security" are still based on jQuery/Entwine logic, with minor bits of ReactJS sprinkled in (e.g. the new TreeDropdownField ReactJS component). In order to provide a consistent developer experience in the CMS, we need to finish this transition.
The CMS UI has often been heavily customised through jQuery/Entwine, so this transition will require many modules to rewrite view logic. It's important to ensure that the same level of customisation is possible with ReactJS. See https://docs.silverstripe.org/en/4/developer_guides/customising_the_admin_interface/reactjs_redux_and_graphql/ for our approach to this.