Responsive images recipe

Huge +1 to this. We need to make life easier to FEDs and provide good defaults for the rest.

I think shipping with Olivero responsive image config is a good idea if we are shipping with Olivero. Why don't we think core should ship with those? Core already ships with Olivero specific blocks for example.

That's a good point, I think we could probably include these in Olivero's default config?

Overall responsive images will be covered by the media management track, and/or the individual content type tracks. But should we create a core issue for updating Olivero to use responsive images anyway?

But should we create a core issue for updating Olivero to use responsive images anyway?

The only thing Olivero-specific is the break points. The actual configuration, although maybe it could be shipped with Olivero, would be in the content types etc. which ship with the standard profile. I'm assuming Drupal CMS is going to completely replace the standard profile, or at minimum its constituent parts with recipes.

Yes, Drupal CMS will. That's a requirement we've documented and will be covered by the work tracks. Do we want to update Standard profile also? Or not worry about it since we are addressing it in Drupal CMS?

If Drupal CMS is going to use Olivero, then it probably makes sense to ship Olivero / core with the responsive images recipe for Olivero, and then rely on that in Drupal CMS - that way it would be possible to build up other non-Drupal CMS recipes that depend on it without an additional dependency.

Moving this over to the Drupal CMS queue so we can track the aspect of what changes would be needed in core.

I'm updating this from plan to task. We will ship the first version with Olivero breakpoints.

There are also some thoughts about breakpoints, containers and grids on this issue https://www.drupal.org/project/drupal_cms/issues/3468896 📌 Define a consistent set of breakpoints, contained layout rules and grid rules for rendering media Active to follow up later.

Question: should this be a distinct recipe? I feel like this should go into the existing drupal_cms_image_media_type recipe, the purpose of which is to make images generally more usable and robust. This feels like it fits into that mission.

@phenaproxima I’m not sure it makes sense to have a recipe for each media type. Potentially the image styles should go into the base recipe, even. I’m going by a very loose definition of recipe and keeping an open mind. I think we can make better choices when we see how the configuration and dependencies look. I intend to ask for feedback on that very soon.

This is implemented as part of https://www.drupal.org/project/drupal_cms/issues/3487391 📌 Implementation of the initial Media Management Proposal Active

Iteration one is based on existing Olivero breakpoints. There are some improvements we could make described in https://www.drupal.org/project/drupal_cms/issues/3488359 ✨ Support retina devices and improve responsive image styles on mobile Needs review

So I think this is a duplicate since it's covered in 📌 Implementation of the initial Media Management Proposal Active