In reply to Just A Guy.

Have to agree with you there. The larger a site, its complexities and the more users of mixed abilities, the more the odds go up that something will go awry.

There seems to be an misconception in the tech industry that any body and every body can be a genius user/programmer. The reality is a lot different. The cognitive load is often too much for those either new to, or unwilling to learn and engage properly. I am not saying that we are dealing with rocket science. It definitely is not that complicated.

I would say that with any of the editors, classic, block or whatever comes with a page builder, they do have their demands. To mitigate against this the best UX possible needs to be applied. The team behind the block editor aren't doing us any favours by ignoring certain use cases.

You mention a site with 5 CPTs. I would often have a post type that is set up primarily for data entry, designed for the controlled capture of information in a concrete format and then fronted with a template to display all this in a uniform manner across all post instances. This mitigates against complete disorder on the site. The way that the block editor is implemented in WordPress it appears above any custom field groups designated in a CPT, inviting users to go wild with free form content. To this end I created my own rudimentary plugin to style out the block part of the editor. I would rather see the Gutenberg team address these practical matters rather than FSE which does nothing for me. I can achieve full site editing in much more enjoyable way with a good page builder.

To a degree you are correct in saying that Gutenberg still seems like a tool to edit blogs about making Gutenberg.