Ok, so no, it isn't 2022 yet, but with how crazy things have been the past few years, I'm just going to pretend we'll actually make it to 2022 relatively unscathed. In my mind, the process of moving to a new theme was going to slowly play out over the holidays, but things kinda progressed quickly and while I'm sure there's still a few things left to tweak, if you're reading this then you're experiencing the new site now.
I've blogged a few times now about integrating Adobe PDF Services with Eleventy, but so far my examples have either been for supporting existing PDFs or converting documents into PDFs for a consistent viewing expirement. Today's test is yet another example of something that may not be a good idea, but it worked, and it's cool, so I'm sharing it!
As I've done every few years, I'm in the process of working on a new look for this blog. I figure it's going to take a while to get it set up properly. In the past I've simply made a copy of my site and worked there when I had free time, but today another idea occurred to me. As the title says, this may be a bad idea, but hey, it worked on my machine so surely I should share with everyone, right?
With Eleventy 1.0 coming soon, I thought I'd take a look at the experience of upgrading an existing implementation to the latest version. As I've warned, Eleventy 1.0 is still in beta so the details may change, but I figured it was safe to give it a try on my own site (the very place you're reading this post). Eleventy is shipping a tool to help with that process, and I cover that a bit later, but me being who I am I just went ahead and Leroy Jenkins the process.
Ok, today's Eleventy 1.0 post (remember, it's still in beta and this may change before release) is a short one. I was looking over the post on 1.0 features and wanted to learn more about this: