Structured format support should be tied to format-specific sub-UI's
|Reported by:||DrewAPicture||Owned by:|
Since we're now making all 9 formats accessible to users regardless of theme support, all of the sub-UI's such as the meta field groups and media insertion workflows are also accessible regardless of declared theme support.
At this point, declaring structured-post-formats support really only serves to short-circuit core output for a select few of the formats. And so, if a theme isn't supporting structured data for some of the formats, users will be adding structured data that likely won't be handled by their theme, creating confusion.
We should tie declared support for structured formats to their respective sub-UI's.
IMHO, I think the best solution is to keep the sub-UI's visible but have some kind of obvious notation that the theme doesn't support handling structured data for that format with maybe a reference link for extending their theme to support it.