Each entry in the “Gems in the rough” series is a collection of tips, explanations, and/or idle observations which I hope will be at least somewhat useful to those of you with websites built by static site generators (SSGs).
The inaugural Eleventy Meetup occurred earlier this week, and it was a blast. We heard interesting talks from Eleventy creator Zach Leatherman and Mike Aparicio of 11ty.recipes fame (and Mike’s dog, too, albeit briefly). A good time was had by all. If you have the slightest interest in Eleventy, I urge you to check the Meetup site and sign up for the newsletter so you can be advised of future sessions.
Things are not great in the world of Mozilla Firefox right now, and they got even sadder this week with news that, according to StatCounter, Firefox’s share of the browser market in June dipped below that of Microsoft Edge and is nearing that of the browser that ships with Samsung phones (which I’d guess many Samsung users eschew in favor of, yep, Chrome):
As for the elephant in the room represented by these numbers: we’ve clearly reached a phase of browser use like that of the “Internet Explorer is the internet” days where Chrome’s massive and non-imperiled market share is concerned. Barring outside action by regulators that could affect this in ways not currently expected, I guess we who build websites will just have to hope our new insect overlords don’t abuse this. (Yeah, right.)
It escaped my notice until this week that Microsoft’s Azure Static Web Apps service has been in general availability for two months. On learning this, I decided to give ASWA a try with the same Eleventy-based test repo I use on various Jamstack-savvy hosts.
Getting signed up was, well, challenging, as one tends to find for most things Azure; and the build process was lengthy1 and supports only a limited number of SSGs, not including Eleventy as of now. Still, I got it going.
In my tests so far, the ASWA site’s performance is so-so, especially compared to that of hosts with far less up-front hassle. It’s not terrible, but I’d have expected more from an Azure-hosted site. Will keep a watch on it but, for now, I’m of the opinion that Microsoft is content to let the usual Jamstack hosts lead the way since ASWA probably doesn’t fit its business model all that well.
On one of my at-least-daily visits to the Eleventy Discord, I noticed a link to “Emails, not comments” by Luke Harris. The article described how, having decided not to have a commenting platform on his Eleventy site anymore, Mr. Harris made it a one-click action for anyone to reply to his articles by email. (He’d probably want me to add that he got the idea from Kev Quirk’s site, as the linked article duly notes.)
The process was both appealingly simple and, to me, geekily interesting; so I stole, um, adopted his approach — as you can see at the bottom of this post, as well as all other pages on the site using the same template. Thank you, sir!
To be fair, I should note that it depends on GitHub Actions, which in my experience adds about ninety to 120 seconds to the process on its own. That said, a build process taking nearly three times as long on ASWA compared to a similarly GitHub Actions-fueled one on a CloudFlare Workers site doesn’t augur well for Microsoft’s setup right now. ↩︎
Commenting by giscus.