Just a quick one to introduce Cheatsheets: a new part of this site where I’ll record anything that took me a while to find the answer to, and would probably take me a while again had I not done the recording. I’ve started cheatsheets for Jekyll, Eleventy, and Intersection Observer. It’s not the neatest list nor is it the cleanest taxonomy. It’ll have to do for now.
Jekyll (which this site currently runs on) seems to be fading into obsolescence. I’m wary of putting too much effort into the current site (beyond writing posts, which are easily transported) because of the sunk cost risk later on. In other words: I know I’ll need to get off Jekyll eventually and want to make it as painless as possible to do so. Adding to the site architecture means more work later on.
I’m getting pretty good with Eleventy. Building the Future Super site on Eleventy is helping to build that muscle. How long until Eleventy follows in Jekyll’s footsteps though? (Probably long enough to warrant the move. But still…)
I’ll rip off the Band-Aid soon enough. Until then (as a general principle) I’m getting more okay with starting from nothing, then sprinkling on generators and frameworks when—and only when—they are necessary. Jeremy Keith says it well:
Instead of reaching for all-singing all-dancing toolchain by default, I’m going to start with a boring baseline. If and when that becomes too painful or unwieldy, then I’ll throw in a task manager. But every time I add a dependency, I’ll be limiting the lifespan of the project.