I guess (without proof) #Eleventy builds including assets bundling/minifying could be accelerated with memoization.
Did this for the slugify filter (I use @sindresorhus's one instead of the default) called multiple times with the same string:
https://github.com/nhoizey/nicolas-hoizey.com/blob/master/src/_utils/slugify.js
This is so great that #CloudCannon is now sponsoring #Eleventy, and hiring @[email protected] as a Developer Advocate! 🥳
https://cloudcannon.com/blog/cloudcannon-the-official-cms-partner-of-eleventy/
Oh… you need to quickly start a new #Eleventy project on your computer?
Asuming you already have npm installed, here's how to use my Pack11ty starter/plugin:
npm create pack11ty@latest your-project-nameEasy enough? 😁
Details on https://pack11ty.dev with other solutions for Netlify, Vercel, StackBlitz, etc.
If someone is creating service workers with #Workbox recipes and injectManifest, a build with #esbuild, and doesn't have any issues, I'm interested! 😅
I have a very strange issue:
https://github.com/GoogleChrome/workbox/issues/3207
Bonus points if this is with #Eleventy
Some things I wish people mentioned when writing about #Eleventy usage, moreover concerning assets bundling (Sass, JavaScript, etc.):
This is really important for sites with many contents/pages, build speed, and site performance.
How I built my own excerpt for Markdown content in Eleventy
I was not really happy with Eleventy's native excerpt solution requiring just a separator and having the excerpt content preserved in the content, without any way to style it differently. So I tried different alternatives, and settled on a solution with some Markdown-it plugins and a bunch of regexes.