In reply to Sheila.

So does Divi, Beaver Builder, Thrive Architect, Elementor, Visual Composer and many other PageBuilder tools deliver now reusable templates Gutenberg is late to the game and still does not have the facilities for managing and display, and globalizing templates that many of the PageBuilders have.

It seems that WordPress is devoting so much effort to duplicating functionality that is already available and then according Gutenberg the reward for being late - it goes core and gets all the associated privileges of core.

This programming duplication effort could be better spent on going to the Cloud, supporting Kubernetes, Elastic Search, Kafka, and other messaging and data transfer protocols much more functional and robust than the RestAPI 2.

For WordPress to become the Web's Operating System - or even Frontend - it must embrace the cloud, containers, and messaging with robust data interchange that is currently fast emerging. I was at AWS, Microsoft Azure and most recently Google Cloud Platform, and WordPress was treated as an afterthought by all three principle forgers of the Webs future.