One of the biggest headaches of responsive design has been dealing with images. Thankfully our work on the Responsive Images Issues Community Group has resulted in a rock-solid set of elements and attributes to address all of your adaptive image needs. My company, Easy Designs, recently redesigned Nichols College’s website and that project just happened to coincide adaptive images landing in Blink (the rendering engine that powers Chrome and Opera). Naturally, we jumped at the opportunity to use them.
Most Nichols College sites run on EllisLab’s ExpressionEngine, a solid little workhorse of a CMS we’ve been using for years. We love it because it gives us complete control over the markup it generates. Now EE offers some pretty decent file management and image manipulation utilities out of the box, but the options it provides were not enough to handle our adaptive image needs; we needed backup. Causing Effect’s CE Image add-on is reasonably priced and offered exactly the functionality we needed to make our adaptive image dreams a reality.
\nI won’t bore you with how to set up CE Image as there is documentation on that, but I will walk you through two different responsive image use-cases we had and how we addressed them using this add-on.
\nThe first use case we had was a series of large, focal images. You can find different examples of them on the homepage and landing pages (like this one for Admissions). The first pass on making these images adaptive involved the picture element for which the spec is known. The markup we were generating was based on the pattern outlined for Picturefill, a JavaScript polyfill that implements adaptive images in browsers that don’t:
<picture class=\"page__image-header__photo\">\n <!--[if IE 9]><video style=\"display: none;\"><![endif]-->\n <source srcset=\"about_940_343_int_s_c1_full.jpg\" media=\"(min-width: 40em)\" />\n <source srcset=\"about_800_350_int_c1_medium.jpg\" media=\"(min-width: 20em)\" />\n <source srcset=\"about_480_350_int_c1_small.jpg\" />\n <!--[if IE 9]></video><![endif]-->\n <img src=\"{made}\" alt=\"\" />\n</picture>To get to that point, however, we needed to use CE Image to generate (and cache) the specific sizes we needed:
\n<picture class=\"page__image-header__photo\">\n <!--[if IE 9]><video style=\"display: none;\"><![endif]-->\n {exp:ce_img:pair src=\"{content_focal_image}\" filename_suffix=\"_full\"\n width=\"940\" allow_scale_larger=\"yes\" crop=\"yes\" interlace=\"yes\" cache_dir=\"/\"\n }\n <source srcset=\"{made}\" media=\"(min-width: 40em)\" />\n {/exp:ce_img:pair} {exp:ce_img:pair src=\"{content_focal_image}\"\n filename_suffix=\"_medium\" width=\"800\" height=\"600\" crop=\"yes\" interlace=\"yes\"\n cache_dir=\"/\" }\n <source srcset=\"{made}\" media=\"(min-width: 20em)\" />\n {/exp:ce_img:pair} {exp:ce_img:pair src=\"{content_focal_image}\"\n filename_suffix=\"_small\" width=\"480\" height=\"360\" crop=\"yes\" interlace=\"yes\"\n cache_dir=\"/\" }\n <source srcset=\"{made}\" />\n <!--[if IE 9]></video><![endif]-->\n <img src=\"{made}\" alt=\"\" />\n {/exp:ce_img:pair}\n</picture>Not what’s a lot of code, so let’s just look at one segment of that jumble:
\n{exp:ce_img:pair src=\"{content_focal_image}\" filename_suffix=\"_full\" width=\"940\"\nallow_scale_larger=\"yes\" crop=\"yes\" interlace=\"yes\" cache_dir=\"/\" }\n<source srcset=\"{made}\" media=\"(min-width: 40em)\" />\n{/exp:ce_img:pair}This is an example using CE Image’s tag pair option, which lets you control the markup output. In the opening tag, we set several properties:
\nsrc is the path to the original image uploaded by content authors;filename_suffix is the suffix we want added to the cached file to differentiate it from others in the cache (and make the files more easily scannable);width is our desired output width for the generated image;allow_scale_larger does exactly what you’d expect: it dictates whether or not CE Image should scale the image to reach the desired width;crop tells CE Image whether it’s okay to crop the image;interlace tells CE Image to use image interlacing (which can speed load time); andcache_dir tells CE Image where to store the cached image (in relation to our global configuration)Then, within the tag pair is the source element with the srcset value set to the path to the file CE Image generated (referenced by the made variable) and the associated media query.
Multiply that a few times for the different sizes and you have the full picture element.
Now that’s all well and good, but shortly after launch, Eric Portis wrote an amazing post explaining how the srcset and sizes attributes operate and it cleared up a lot of my confusion on the matter. He convinced me that the age-old img element, with these new attributes, would be far more maintainable. With a fire in my belly, I rewrote the markup:
<img class=\"page__image-header__photo\" alt=\"\"\n {exp:ce_img:pair\n src=\"{embed:image}\"\n filename_suffix=\"_small\"\n width=\"480\"\n height=\"320\"\n crop=\"yes\"\n interlace=\"yes\"\n cache_dir=\"/\"\n }\n src=\"{made}\"\n srcset=\"{made} 480w,\n {/exp:ce_img:pair}\n {exp:ce_img:pair\n src=\"{embed:image}\"\n filename_suffix=\"_medium\"\n width=\"800\"\n height=\"600\"\n crop=\"yes\"\n interlace=\"yes\"\n cache_dir=\"/\"\n }\n {made} 800w,\n {/exp:ce_img:pair}\n {exp:ce_img:pair\n src=\"{embed:image}\"\n filename_suffix=\"_full\"\n width=\"940\"\n allow_scale_larger=\"yes\"\n crop=\"yes\"\n interlace=\"yes\"\n cache_dir=\"/\"\n }\n {made} 940w\"\n {/exp:ce_img:pair}\n >The CE Image behavior is exactly the same, but the resulting markup is much clearer:
\n<img\n class=\"page__image-header__photo\"\n alt=\"\"\n src=\"about_480_320_int_c1_small.jpg\"\n srcset=\"\n about_480_320_int_c1_small.jpg 480w,\n about_800_350_int_c1_medium.jpg 800w,\n about_940_343_int_s_c1_full.jpg 940w\n \"\n/>The added bonus of this approach is that I am not hard-coding any media queries and the browser gets to make the ultimate decision of which image to request. All I am doing is telling the browser the image options and their respective widths within the srcset attribute. As all of the images take up 100% of their containers, I didn’t even need to use the sizes attribute. Easy peasy.
Not every image adds something to the page. Some are purely optional, a visual enhancement. In order to reduce the size of pages on smaller screens, we often choose to “lazy load” certain image assets after page load, when we know there is enough room to display the image or when we feel it would be an enhancement to the design.
\nNow some of you might be wondering: Why not just display:none below a certain threshold? Well, I’ll tell you: images that are hidden with CSS are still requested by the browser. That means users who don’t see the images are still paying to download them (whether in terms of time waiting for the page to render or actual money on a metered connection). That kinda sucks for them. We should show our users a bit more respect and only request the images when we need them.
We wrote a lazy-loading image script a few years back and have battle tested it on numerous sites to great success. It’s all based on a simple markup pattern:
\n<div\n class=\"module__image image--lazy\"\n data-image-src=\"Tim-Smith_220x140_220_140_int_c1.jpg\"\n></div>The data-img-src attribute defines the path to the “nice to have” image and then the JavaScript adds the image element into the page when the appropriate conditions are met:
<div\n class=\"module__image image--lazy\"\n data-image-src=\"Tim-Smith_220x140_220_140_int_c1.jpg\"\n data-image-loaded=\"\"\n>\n <img alt=\"\" src=\"Tim-Smith_220x140_220_140_int_c1.jpg\" />\n</div>Pretty simple. It even supports srcset:
<div\n class=\"module__image image--lazy\"\n data-image=\"about_480_320_int_c1_small.jpg\"\n data-image-srcset=\"about_480_320_int_c1_small.jpg 480w,\n about_800_350_int_c1_medium.jpg 800w,\n about_940_343_int_s_c1_full.jpg 940w\"\n></div>The full documentation is up on Github.
\nImplementing this in the context of CE Image was a breeze and builds on the source pattern I showed earlier:
{if testimonial_photo} {exp:ce_img:pair src=\"{testimonial_photo}\" width=\"223\"\nheight=\"140\" allow_scale_larger=\"yes\" crop=\"yes\" interlace=\"yes\" cache_dir=\"/\" }\n<div class=\"module__image image--lazy\" data-image-src=\"{made}\"></div>\n{/exp:ce_img:pair} {/if}We are only just beginning to scratch the surface of what’s possible with adaptive images and I am sure we will come up with newer, better ways to do this stuff. Heck, there may even be an adaptive images add-on in the pipeline for ExpressionEngine. But, in the meantime, if you are trying to implement adaptive images with ExpressionEngine, CE Image is a good way to go.
\n","url":"https://www.aaron-gustafson.com/notebook/adaptive-images-in-expressionengine-with-ce-image/","tags":["web design","responsive web design","ExpressionEngine","progressive enhancement"],"date_published":"2014-11-21T23:18:23Z"},{"id":"https://www.aaron-gustafson.com/notebook/jail-ing-images-in-expressionengine/","title":"✍🏻 JAIL-ing images in ExpressionEngine","summary":"A while back I came across a link to Sebastiano Armeli-Battana’s jQuery Asynchronous Image Loader ( JAIL ) and filed it away to revisit when I had some time. I finally made some time this weekend.","content_html":"\n\tA while back I came across a link to Sebastiano Armeli-Battana’s jQuery Asynchronous Image Loader (JAIL) and filed it away to revisit when I had some time. I finally made some time this weekend.
\n\nJAIL’s a cool little script that takes care of lazy loading images for you in order to speed up initial page rendering. To use it, you implement the following markup pattern:
\n```html\n![\"\"/](\"foo.png\")
\n