Warn users of Classic blocks to convert to Gutenberg blocks

[JessieHenkes]

Explanation

Users of Classic Blocks in Gutenberg do not see any assessment results, because we can't identify and analyse these blocks. Therefor we want to warn users of those blocks that we do not support those blocks and that if they want to see some assessment results, they need to convert this specific block to a Gutenberg block.

Technical decisions

• We need to create and push a warning to users, to make them convert to Gutenberg if they face problems with Classic blocks
• We do NOT adjust the researchers in order to make them analysing those classic blocks
• We will not include the texts of these blocks in the analysis: they will be fully ignored

Feedback?

@nataliashitova @manuelaugustin @hansjovis: does this description and proposed solution cover the discussion we had? Please feel free to add!

[hansjovis]

I cannot seem to reproduce the issue that Classic Blocks do not get analyzed.
Do we have a bug report that I can use for context?

[nataliashitova]

Design issue: https://github.com/Yoast/design/issues/609

[nataliashitova]

The current situation is that Classic blocks do get analyzed for Yoast checks, but not consistently with the normal Gutenberg text blocks.
If we throw a warning about no support for Classic blocks and need to convert to Gutenberg blocks while still taking the content of the Classic blocks into account to some extent that will be confusing.
In my opinion, this issue should also include a task "Refrain completely from analyzing Classic blocks in the Gutenberg editor".