You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 15, 2018. It is now read-only.
We need to update the way we handle images to provide the necessary data to work well with the new responsive images spec, primarily the <picture> tag as per the MDN doc and HTML spec.
Currently, we may upload multiple images to content in our CMS, and ideally we would extend that existing functionality in order to enable the following:
Uploading multiple images, each of which may be translated into a <source>
Providing a field on the model for each image which may be mapped to the media= attribute.
Related to point 2 above; the ability, possibly via fixtures, to create reusable media queries, and obfuscate the complexity of media queries from the content manager, thus allowing greater flexibility if required and at the same time enforcing a standardised set.
Thus, given the following data in the CMS:
image1.png | No media query fixture
image2.png | Desktop media query fixture
image3.png | Mobile media query fixture
image4.png | Tablet media query fixture
...the data would be mapped in the markup as such:
In the above example, <size> refers to the photologue generated size variation. Each srcset would have a range of sizes as defined in the photologue fixtures, and were omitted from this example for brevity.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to update the way we handle images to provide the necessary data to work well with the new responsive images spec, primarily the
<picture>
tag as per the MDN doc and HTML spec.Currently, we may upload multiple images to content in our CMS, and ideally we would extend that existing functionality in order to enable the following:
<source>
media=
attribute.Thus, given the following data in the CMS:
image1.png | No media query fixture
image2.png | Desktop media query fixture
image3.png | Mobile media query fixture
image4.png | Tablet media query fixture
...the data would be mapped in the markup as such:
In the above example,
<size>
refers to the photologue generated size variation. Each srcset would have a range of sizes as defined in the photologue fixtures, and were omitted from this example for brevity.The text was updated successfully, but these errors were encountered: