11ty wasn’t right for me

In 2022 I migrated to 11ty, a flexible static site generator. I thought it perfect but I was wrong and it took four years to recover 😪

Let’s be clear, my last post on this was true: I loved deploying 11ty. It was 100% right to move to a SSG, exfiltrate the content from a claggy database into markdown files, twisting the excellent markdown-it library to handle a decade of custom tags and weird oddities, and 11ty Just Kinda Sorta Worked™. A quantum leap from the rigid Django system I’d been using since 2010.

My elation masked the ugly bits, until they got in the way.

The shame of being stuck on a platform I’d just eulogised for contributed to my stopping writing altogether. Not a sole cause, by any means, but every time I opened the site to write, all I could see was stuff I needed to fix.

The lesson of the story isn’t Astro

Wait, this incomplete pile of complaints is a lesson? Didn’t I move to Astro? Well, yeah, but it’s okay that 11ty didn’t work for me. I’m not angry at Zach & co. — they helped me as much as they could with a system that I’m sure does what they need. They owe me nothing.

I failed but I didn’t Fail Fast.

I knew four years ago that 11ty wasn’t working for me. Rather than shop around, I convinced myself that I’d fix it one day. It was a perennial project for another day. In putting it off, I nearly ruined one of my favourite hobbies. I missed every cue to correct these oversights, and lied to myself that I’d come back to it.

As a three time platinum-selling parent, a key skill is being honest about mistakes, learning from them. If you don’t accomplish this cycle, you get stuck in ruts. The longer it goes on, the more peripheral damage.

This site does run Astro now. It took a heck of a lot of work to port my Markdown code over, and indeed was only just made possible this year inside Astro. Maybe I’ll write about it one day.