• Part of Block API #41236.

What problem does this address?

As a small publisher in media, WP introduces extensive new features and functionality that we do not need. Very often it creates problems by adding featured within the Editor that we do not support on the frontend template.

Disabling such features is often not possible, or creates overhead on the WP UI that can break between releases.

Some examples:

An article template supports numerous blocks but we don't support most over 60 of them ('core/post-content','core/post-author', core/query-pagination', 'core/comments-title', 'core/home-link', 'core/calendar', 'core/column' etc.)

We have to manually unregister each block, and we need to manually add new blocks as they are added in each release. There is a disconnect between registering/unregistering blocks by PHP or JS.

Likewise, blocks themselves change. We support the Quote Block but in version 6.2 that block also support Images as the quote content. Our site design doesn't allow for it, nor do we need it. Separately I would argue that the Quote Block should never support it. There is no obvious way to disable the image aspect to Quotes.

These changes that we cannot control create confusion to our users, writers and editors, when they use features that break the page, or don't work at all to expectation.

I love WordPress. I had Quartz built on it, then I had The New Yorker migrate to it (since left due to custom corporate CMS), and I just had Rest of World built on it.

What is your proposed solution?

As a publisher/engineer, we need attention to configuration options. They appear to be missing entirely, or an after-thought, on core features that are vital to us.