This is interesting and kind of weird at the same time. I think Google has missed the point completely with this. While it is true that the future of documents

This is interesting and kind of weird at the same time. I think Google has missed the point completely with this. While it is true that the future of documents is API driven and task automation will meet document editors, this is simply not the way forward. It's like Henry Ford giving people who are looking for faster and more economical transportation an assembly line instead of a car. Here is why: - Task automation, by definition is supposed to save time and money. By building a developer API, you still need developers (whose time costs more money!) to build and maintain your automations. - The underlying document model itself cannot be accessed. So what they've made is some kind of HandleBarJS way of creating documents and filling them in. I'm working on something in a similar space (https://afterclass.co https://afterclass.co) and we've had to build our own document model and automation handler to work around these two problems. Would be interesting to see how this pans out :)