Norske

Greetings, @andraganescu. Thanks for your reply.

Those block templates look useful for those who accept the block editor paradigm as a fact. But the problem is not about managing blocks. It’s about supporting custom page layouts created by content-managers. End user is not responsible for design issues, usability and future redesign difficulties. Yes, templates may be a nice workaround, restricting unqualified creativity. But I don’t need a workaround as I don’t need those blocks at all. Page layouts are sometimes based on usability researches and commercial KPIs. We expect CMs to manage the data, not the blocks.

For now I keep ~4 sites ‘frozen’ on WP v4.x. (those are the most risky) and ~20 sites have complex fallback to Classic Editor. Experimental projects with Gutenberg showed 100% negative reaction from my clients even after 2 weeks in use. They find block editor too complicated and time wasting. They prefer filling 10-15 simple fields separated into 3-4 tabs then manipulating 10-15 blocks in one frame.

In future I’d rather switch all those projects to ClassicPress, if that fork will survive for a year at least. Hope so. If not, I’ll probably offer my clients a migration to Drupal or maybe a custom solution based on Yii2.

WP is too risky now.

But thank you for your post, anyway!

Oh ?? Really lurked UCP’s webpage for the docs, but didn’t even look through the code. Shame on me ?? Thanks a lot, will try it.