The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jorgefilipecosta <jorgefilipecosta@git.wordpress.org>
Co-authored-by: jameskoster <jameskoster@git.wordpress.org>
Co-authored-by: jasmussen <joen@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Size Change: +442 B (+0.03%)

Total Size: 1.77 MB

_{compressed-size-action}

#65107 is very relevant to the conversation here as it could significantly increase the likelihood of pages having a featured image.

That coupled with the poor performance of loading full page previews leads me to think we shouldn't change the default preview as a part of this PR. That feels like a detail to discuss separately.

The user can switch the media field by showing a different media field. E.g: if we go to the view settings and show the featured image field the featured image becomes the media field.

This interaction doesn't feel great right now because toggling the featured image field has a totally different outcome to toggling any other field. It doesn't feel like you're choosing between one option or another. The way I'm looking at this is; there are two properties associated with the Preview field, and the user can choose between them. The UI should reflect this.

How do you feel about something like this mockup:

Meanwhile, the codebase changed a lot, I proposed a new version of this PR taking into account its feedback at #67278.