As part of the effort to determine Gutenberg’s compatibility with an existing site’s content we need to drill down into each individual post to evaluate which editor would be the recommended editor for the current content. From these figures we can attempt to determine the overall compatibility of the Block editor with the site’s content.

Each post can be evaluated for compatibility with the Block editor and can be assigned a preferred editor state.

Any post which has not yet been analysed may be considered to be in an Unknown state - equivalent to A.

Each ‘editable’ post type can also be classified as A, B or C
For the [content] shortcode 5 different post type classifications were produced.
There should have been 6.
This table maps the classifications.

Note: Post types classified as B do not yet exist.

Proposed solution

• Each editable post will be assigned a preferred editor meta field, key _oik_block_editor.
• This will be based upon ‘opinions’.
• For B or C this value may be mandatory
• The meta box will explain the opinions.
• Any user may choose to force a mandatory opinion of B or C.
• The stored value may be used to control which editor the user can use.