Policy proposal: content types provided by recipes should provide opinions about metatag configuration

Problem/Motivation

We currently have seo_basic and seo_tools, but often particular content types should have more specific configuration, for example to populate schema.org metatag properties that are specific to relevant entity definitions.

Proposed resolution

Recipes that provides content types should provide metatag configuration specifically to optimize the representation of relevant data. For example, an event content type should include tokens mapping relevant data fields to corresponding meta and schema.org properties such as startDate, endDate, location, and so on.