Plugin Directory: Show flag or marker to indicate the plugin has been added to BLOCKS category

[Ipstenu]

I know we're moving to a 'Block' only subsection of the directory, however I believe there will still be a need for the BlockS (with an S) category that shows plugins that contact blocks and other code.

Manually adding by request (and when we notice them) is fine, however since the blocks listing is _random_ (yeah) people can't tell if we really did add them or not, which results in confused emails.

We should have a way to show on the plugin page if the plugin is listed or not. Just a block icon or something, or even "Gutenberg Ready"

It's a low impact/high reward :)

[tellyworth]

How's this, as a quick starting point? The line would only appear if it's in the blocks section, and the number would show the number of blocks discovered in the code.

[Ipstenu]

What happens if they're in Blocks but the block-script hasn't run? Would they show a 0?

[tellyworth]

What's the preferred behaviour? It could show 0, or "unknown", or we could not display that line at all.

[dufresnesteven]

What happens if they're in Blocks but the block-script hasn't run? Would they show a 0?

Does it have to show anything if we are waiting on it?

[Ipstenu]

yes, we do need to show something.

The line would only appear if it's in the blocks section, and the number would show the number of blocks discovered in the code.

Note that the pre-requirement is that the plugin is already flagged as having blocks (this is a category we can set on the backend). So in order to have this, we already have had a human say "Yep, at least one block!" And in order to highlight "Hey, there are blocks in this here plugin!" we want to say ... something?

Maybe Blocks "TBD" when in the category and un-counted.

• if in-blocks, then check for count
• if count gte 1, display block count
• if count == 0, display nothing
• if count does not exist (i.e. hasn't been run), display TBD

[dd32]

I think by now it should be assumed that plugins have a Block for any editor-focused components, plugins not updated in a while are pushed down search results far enough that I'm not sure there's a need to flag the existence (or lack of) blocks anymore..

[Ipstenu]

The (primary) reason for the ask is that we do still allow developers to request to be added to the 'have blocks' list (which is separate from the ONLY blocks list). Without a way to see if that was completed, the developers end up asking us multiple times until someone sends them a backend screenshot. Unless we're removing that section entirely (@otto42 added it) I think we should make a clear note of it.