In reply to Darren Ethier.

Hi,

Like Anthony I work in an agency serving clients in many fields (I'm the co-founder and main web person). I second and strongly agree with pretty much everything Anthony said. For us, Gutenberg is still nowhere near ready for primetime and the WooCommerce's lack of preparedness for it is very concerning. I'm sorry but, at this stage, "we read this feedback and it is considered" or that the sate of blocks extensibility is something "you are aware of and are thinking of" is simply not even close to good enough. It's astonishing to me as well.

That's not even mentionning some much more basic stuff like the abysmal state of UX in WooCommerce checkout like submitting an order shows a progress icon in the middle of the page (sometimes 2 screens above the "Place Order" button where no one sees it on mobile. The number of client complaints we've had about that... User feedback should be contextual and near the user action, that's UX 101.

Then Gutenberg itself is even worse. Just one similar example: saving a Gutenberg page/post (by clicking the "Publish"/"Update" button in the top right) results in the success/fail message appearing in the complete opposite corner in the bottom left. It's such ridiculously bad UX it boggles the mind that Gutenberg has been in core for 18 months... This kind of ridiculous UX is all over Gutenberg. Contextual user feedback, selection and drag and drop visual cues and affordances... that's also UX 101. This is supposed to replace page builders? Wow.

To now learn that WooCommerce blocks are even less ready than that confirms that we made the right decision to not have subjected our own clients to Gutenberg yet and we're not adopting it any time soon.