Off-the-cuff note since this came up recently: how to bundle #JavaScript and #CSS files with content-hashed names using esbuild in #eleventy:
Off-the-cuff note since this came up recently: how to bundle #JavaScript and #CSS files with content-hashed names using esbuild in #eleventy:
The longer I have to deal with 20 min+ builds for my website (it just has lots of images - served remotely from an object storage - by this point that eleventy-fetch and elventy-img have to go through) the more I am unsatisfied with the setup I have come up with for myself.
In theory, images should be downloaded/resized once. In practice cache invalidation and build pipeline limitations (and me not having the time to solve it properly - but I do have time to wait 20 minutes per deploy? Huh.) mean that instead of waiting around 3 mins I wait way longer.
I love #eleventy, but I do sometimes feel the trade-off of using an ssg over a dynamic blog solution like #ghost…
A quick rant about my move to #PageFind on my #11ty site and the process of setting it up
https://jacen.moe/rants/20251112-moving-search-from-google-to-pagefind/

I'm just enough of a narcissist to believe that people deserve to hear the things I have to say, so discoverability is very important to me. To that end, I've wanted to have some kind of search function on my site to make it easier to find older posts. Around two months ago, I added a Google Programmable Search Engine as a temporary measure, but I always had my eye on PageFind in the long term. Today, I finally took the time to implement the PageFind solution into the site.
@amoroso Moving from WriteFreely to Eleventy increased friction for me. I can no longer publish or edit a blog post from my phone and I miss that.
That said, I still appreciate the markdown input format of Eleventy and using git for branches etc. I also have more confidence that I won't lose posts if something goes wrong.
I think this trade-off between friction and features is ok for me, but it needs to be part of a conscious decision when choosing a blog platform.
The latest issue of the awesome 11ty Bundle newsletter includes my recent tutorial on making a image gallery static site with #11ty.
There's also a nice article from @cyberseckyle showing how to embed Mastodon posts.
A few weeks ago I shared a tutorial on how to make a simple HTML gallery and host it online for free.
Here's a version that uses the 11ty static site generator.
https://stefanbohacek.com/blog/making-a-free-image-gallery-with-11ty-and-neocities-org/
#tutorial #gallery #ImageGallery #11ty #eleventy #neocities #WebDev #WebDevelopment #LearnToCode

Last month I wrote a version of this tutorial aimed at people who prefer a simpler, more straightforward setup for their websites without the need to install extra tools or use a command line. As with everything, there are trade-offs to be considered. In this follow-up, I will revisit the gallery project using 11ty, a...
The new facelift on my website is now live.
I have added more color to it. Made it more lively. The footer is a less bland looking and I have added my sites Speedlify score.
Another thing I have added it a share section to each post. This is a plugin I have been working on (soon to be live).
The biggest problem I have with my new vps: The #eleventy img based resizing (I think) means that a build of my blog maxes out the ram (12 GB, 6,99€ exc vat). Which I guess means I will have to upgrade to the next bigger machine (24 GB Ram, 13,99 exc vat).
P.S.: I am also dismayed how much ram is used for a machine outside of builds that does basically nothing, since nobody is visiting the vps based blog yet. And honestly even then… I guess #coolify is relatively heavy (and the idling db, redis, minio to power the dynamic bits of the blog probably don’t help)… makes me think that their “cloud option” is maybe not so bad a deal... I was initially skeptical, as the builds/deploys would still happen on my server, but if coolify uses (it seems) around 60% of my 12 GB ram all the time paying 5€ instead of upgrading my vps might be worth it instead). https://hachyderm.io/@finn_matti/115501969478983016