Note from 7 April 2023

Some things I wish people mentioned when writing about #Eleventy usage, moreover concerning assets bundling (Sass, JavaScript, etc.):

  • Does it run only once per asset, or once per template where the asset is used?
  • Does it run before or after HTML is generated?
  • Does it manage hashes for cache busting?

This is really important for sites with many contents/pages, build speed, and site performance.

  1. Note from 26 October 2024

    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.

    GitHub Pull Request showing 167 changed files with 3,632 additions and 23,478 deletions

    Doesn't “3,632 additions and 23,478 deletions” sound like a big improvement?

    Much less specific code to maintain in the future! 🥳

  2. Note from 19 October 2024

    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.

  3. Note from 16 September 2024

    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!