Note from 19 March 2020
My #Eleventy build time is now down to 37 seconds on average! 💪
A few external data fetches, 1087 HTML pages generated, 1608 simple images <img src…>
automatically transformed into responsive <img srcset… sizes…>
…
My #Eleventy build time is now down to 37 seconds on average! 💪
A few external data fetches, 1087 HTML pages generated, 1608 simple images <img src…>
automatically transformed into responsive <img srcset… sizes…>
…
My photography site is now built with #Eleventy v3, all JavaScript code is migrated to #ESM, and common features I use in all my Eleventy project are now provided by the #Pack11ty plugin.
Doesn't “3,632 additions and 23,478 deletions” sound like a big improvement?
Much less specific code to maintain in the future! 🥳
Looks like I finaly managed to migrate #Pack11ty, my plugin and template/starter for #Eleventy to v3! 🥳
Including replacing all CJS with #ESM, the most difficult part.
Preview: https://11ty3--pack11ty.netlify.app/
Code in branches 11ty3
:
I will now improve the docs, before releasing stable versions.
I have to admit that I'm often sad when I read “Font Awesome” in the code of projects I'm auditing for performance. A fairly heavy font is often loaded to display a few icons, whereas we've known for a long time that SVG is generally more suitable.
But the arrival of Web Awesome, and my enduring admiration for @zachleat@zachleat.com and @leaverou@front-end.social (and their creations) means that their arrival at Font Awesome may well change my epidermal reaction to the name.
Bravo!
I'm now using #Eleventy's screenshot service for my links content, thanks a lot @zachleat@zachleat.com!
But…
…it looks like many screenshots fail, so I get the default image — Eleventy's logo —, as you can see in my #Cloudinary Library… 😅
I don’t want to suggest that my experience was bumpy, mind you — far from it! Overall, I am delighted by how easy it was to move a decade’s worth…