A super quick and simple way to speed up the development experience on 11ty sites as they grow in size and complexity.
I was recently complaining to Ray Camden about the 11ty development experience. My site has grown to several hundred pages and has some complex content relationships. It’s gotten to the point that I have to wait about 15 seconds to see content or code changes I’ve made.
When I’m writing content locally, this is an obnoxious waste of time.
Ray suggested I ignore files I knew I wasn’t going to use while developing. Because my post filenames are all prefixed with a date, I could easily do this by adding an
.eleventyignore file to my project and ignoring posts from previous years:
And then I ignore that file in
⚡ This cut my development builds from 15 seconds to 7 seconds! And reduced subsequent builds to 4 seconds with some caching in my asset pipeline.
It’s not perfect, but a huge improvement. It at least makes this site feel manageable in development once again.
While Eleventy doesn't appear to be built for today's component-driven landscape, here are three approaches we can take to get closer.
What seems like a simple task can be a little tricky to get right with Eleventy. Learn how to add a _redirects file to Eleventy projects deployed with Netlify.
Learn how to take a handful of static HTML files and convert them into templated files that will help you minimize errors and work more efficiently.