posted: Fri, Feb 14, 2025 |
tagged: | | dev | web
return to blog home |
Reference Links:
Today it was time to upgrade 11ty from version 2.1 to version 3.0. I have to say, the process is probably the most seamless and painless upgrade that I've really ever had to do. The team at 11ty has made this process as clean and as easy as possible, and while I've thought about migrating to a SSG like Pelican due to my greater familiarity with Python, I really can't complain about how well 11ty works.
As previously mentioned in my post about using a Static Site Generator, and as documented in my post about upgrading to 11ty 2.0, I don't think I can recommend this solution enough. With the advent of AI-decorated coding platforms like Windsurf AI, (which I am using now) and Cursor AI, the lacking familiarity I have with Javascript is something I think I can work my way around well enough.
Much like before, the process was as follows, with a few minor tweaks for a version number:
I then ran a new build, checked for any errors, removed the additions from above, and done! My package.json file is unpdated accordingly. Easy peasy.
You can find the full upgrade helper documentation here.
With all of the upgrades I've performed in my IT career, which has been going for more than a minute, this remains one of the absolutely smoothest I've ever encountered.
Hats off to the team at 11ty for yet again providing a great experience.
Oh, and for the record, I did try and have Windsurf AI perform a conversion from 11ty to Pelican, and boy oh boy, that was a mess. I reverted my Git changes back to the base and then performed the upgrade. So there may have been an alterior motive, but I'm not disappointed in the results. Maybe it was the earthquake that fired about an hour ago that let me know the heavens were displeased... Or maybe it was the fact that I've been ignoring this blog for a bit more than a minute. Who am I to judge?