Bernie Reiter

Committed to Core in https://core.trac.wordpress.org/changeset/59101.

There's one more instance where we should call `apply_block_hooks_to_content` (rather than invoke more low-level Block Hooks related functions): The Navigation block in Gutenberg. I've filed a PR: https://github.com/WordPress/gutenberg/pull/65703.

Noting here that if we don't want to implement this kind of behavior universally for all taxonomies, we could add an argument to `register_taxonomy` to control it.

> > To allow using just one template to render both that root taxonomy route (/projects), as well as the taxonomy archives for each of the terms in that taxonomy...

BTW as discussed on our call the other day, extending the template hierarchy isn't particularly complex, but very cumbersome, and there are a few different ways to do that. I...

> What's missing to have it ready for review? Really just the two things I've left notes for. Maybe you can weigh in on the [first one](https://github.com/WordPress/gutenberg/pull/63311#discussion_r1679183548); I can work...

I've committed a [changeset](https://core.trac.wordpress.org/changeset/60611) to Core that implements a filter to customize which of a block's attributes are supported by Block Bindings. Thanks everyone!

👋 Here's the GB counterpart PR: https://github.com/WordPress/gutenberg/pull/71820 (which is even more important, since that's what's needed to pick up the server list on the client side). Still WIP 😄

What Carlos said. FWIW, we came close to landing a solution that would have [used the list of blocks that are supported by block bindings as provided by the server...

Thanks @jameskoster, I quite like this! 🙌 Just to clarify, would we still indicate somehow in the canvas that there is an error with a given block (e.g. by greying...