TIL in #Eleventy inputPath gives the path to the source content, not to the template generating the page, when we use pagination… Where can I guet the template path? 🤔
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 [email protected] 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.
I've read the whole documentation for #Eleventy's WebC components: https://www.11ty.dev/docs/languages/webc/
Time to experiment, I guess!