I find it a little hard to put this succinctly, but basically as a dev I get a little nervous seeing all the features in the UI. In my experience any complex editor like that has to be designed around a bunch of assumptions about what kind of site you’re editing, and almost every slightly complex real world site will have aspects that break those assumptions. It could something subtle, like confusion around terminology (imagine being a non-technical editor for a book binding website, and seeing terminology about “bindings”), or features that look like they should do something but for whatever reason don’t have any effect on the components in use. The more complex the editor is, the more likely that certain things will cause confusion when they meet the real world.
Their interface feels easy to start with but can take you very far if you need customization and scalability.
We are far from what they achieve, but that's where we'd love the end up. :D
On the video: first impression is that it's heavily Weweb-built template driven like another Squarespace (especially if I stop watching in the first couple of mins before the bit about design systems) whereas I assume from the description in this thread that the design elements marketers can add and what layouts/colours etc they can choose can be fully configured by devs (and the target audience is teams that want to do this) Ultimately I assume you plan on replacing the tutorial on the home page with a video that's snappier, more benefit-focused and more selective about UI examples anyway?
Thanks for the feedback on the video, it's really useful. Makes me think that on the developer video we should probably start from a blank site and add a custom component in the editor right away.