My life just got a lot busier; I'd really like a maintainer or two to help. I'm not abandoning JPT, I just don't have a ton of time to put into hacking on it.
If you've been learning Ruby and you want to move beyond tutorials and throwaway projects, I'd love to hear from you. I'd be happy to help you gain experience and credibility, if you're willing to help me maintain this project!
If you're interested, contact me: [email protected]
Responsive Images done correctly.
It's simple to throw a photo on a page and call it a day, but doing justice to users on all different browsers and devices is tedious and tricky. Tedious, tricky things should be automated. This blog post further elaborates on that theme.
Jekyll Picture Tag automatically builds cropped, resized, and reformatted images, builds several kinds of markup, offers extensive configuration while requiring none, and solves both the art direction and resolution switching problems with a little YAML configuration and a simple template tag.
Performance: The fastest sites are static sites, but if you plonk a 2mb picture of your dog at the top of a blog post you throw it all away. Responsive images allow you to keep your site fast, without compromising image quality.
Design: Your desktop image may not work well on mobile, regardless of its resolution. We often want to do more than just resize images for different screen sizes, we want to crop them or use a different image entirely.
Developer Sanity: If you want to serve multiple images in multiple formats and resolutions, you have a litany of markup to write and a big pile of images to generate and organize. Jekyll Picture Tag is your responsive images minion - give it simple instructions and it'll handle the rest.
2.0.3 April 1, 2021
2.0.2 March 31, 2021
2.0.1 March 31, 2021
2.0 March 25, 2021 - Migration guide
format_qualitydefault settings for webp, avif, and jp2.
media_presets. They are now officially and only
1.14.0 January 10, 2021
Writing code is only part of the job; often the harder part is knowing what needs to be changed. Any and all feedback is greatly appreciated, especially in regards to documentation. What are your pain points? See the contributing guidelines, or the issues page for more.