Dynamic social share images using Cloudinary
Automatically generate unique Open Graph images for each page of your website
Responsive, Performant Images for the Web
Learn to optimize your images for the web in this video from PerfMatters Conf.
, updated by 
Sia Karamalegos
Want to learn how to make your images more responsive and more performant? Haven't gotten a chance to read that book/article/doc on web performance for images yet?
I spoke at my first virtual conference, PerfMatters Conf, and luckily they recorded it. This talk is a great intro into all things images for the web. Enjoy!
In this talk, I focus on the underlying concepts in HTML and CSS for serving responsive images, which you can take with you no matter which tool you use. Which file formats suit which image types best? How can you use art direction in images to show the best image for a viewport layout?
Hi, I'm Sia.
I'm a freelance performance engineer and web developer, and I'm available for your projects.
Hire meYou might also like
What to know about AVIF on Cloudinary
Start using AVIF today with Cloudinary. Learn about your options, the tradeoffs, and how to overcome slow transformations.
Optimize Images in Eleventy Using Cloudinary
Set up responsive images in Eleventy using Cloudinary and Eleventy shortcodes
Webmentions
If you liked this article and think others should read it, please share it.
❤️ 11
🔁 3
💬 7
Sia Karamalegos
Thanks! source
Keith J Grant
oh interesting. hmm source
Chris "I Dissent" Aldrich
Sometimes Brid.gy can miss tweets. Here I suspect it’s because of the t.co wrapping as well as searching the entirety of the stream for your URL since it was a direct reply to your original tweet. Ryan Barrett may have… boffosocko.com/?p=55785332 source
Ryan Barrett
Thanks Chris! Bridgy actually handles t.co wrapping fine. Not easy to debug this one since it's half a year ago. It would be here or nearby though, and it's not: brid.gy/twitter/TheGre… source
Sia Karamalegos
I found a recent one with my tweet as the origin, but I wasn't sure if those were left out by design? source
Ryan Barrett
Sorry, just noticed that Chris retried it. Looking at Bridgy records, Bridgy did originally see it on 2020-06-17 23:17:44 UTC-7. I don't have more detailed logs from that far back, but maybe it hit a transient error discovering or sending to your webmention endpoint? Not sure. source
Ryan Barrett
Right, original tweets are a separate issue from other people linking to your site like https://t.co/XRinqcoQck. Original tweets are omitted by design since they're considered the "same post." That's pretty generally accepted IndieWeb thinking, not Bridgy specific. source
These are webmentions via the IndieWeb and webmention.io. Mention this post from your site: