Whew, I return to the comfortable confines of WordPress where I can happily tag my CSS excursions.

While my Jekyll/GitHub Pages experiment was a fun challenge, my results-to-development ratio was far too low! I honestly had no plans to learn JavaScript on the fly, yet, to get some basic functionality online or fix something that should just work, I had to pore over all sorts of Google results…and when you start seeing your own site pop up in Google about the issue you're having, you know there's some scant info out there.

So, I return to WordPress with all the easy extended functionality that it provides! I'm paying $3/month to host my stuff. I think it's worth it, especially as I just broke from ProtonMail which charged $5/month just to use a custom domain for email.

And NOW, I can focus on content generation and what I want to accomplish for the rest of the year including what I want to do with the Expeditions.

The 13th Expedition is not about workouts. At the outset, it has been a cruise into the rays of the night turned speedboat into the horizon. I know I made a declarative last week as to how I was developing a program—I still am, by the way—but, again, I am wooed by the novelty of having an entire Expedition based on no workouts (sans the first few days) in an unmonitored calorie context, while listening to my hunger. I recognize that workouts call for more resources. And yes, in the past, I had an ironfist will to maintain that 1000-1200 ceiling.

All that aside, my first workout will come on Thursday, July 30—I know, it sounds as though I'm trumpeting it more than I ought. It'll be the start of The 14th.

...and tada! I am now on GitHub Pages, though my audience may not know that until tomorrow once the DNS propagates across the Internet.

Late last night, I wiped out my WordPress install for this move, but this morning I had second thoughts. After doing the worn WP-CLI route and updating the configs, specifically regarding comments, I realized, "This is a bloaty hassle."

Therefore, I just tore it all down and...well, here I am.

There's a few tweaks I need to do. I went with the Minimal-Mistakes theme just because I already had it customized to my CSS/HTML, though I'd like to find a DataTables solution that works...assuming I don't go ahead and run down what in the theme breaks the functionality. Right now, I'm just going with a bland non-sortable markdown table.

I'd like to move on from site setup/design to a greater fitness orientation. Once the site is established, updates will be easy.

I'd like to find use a clockdown clock solution for The 13th Expedition's weigh-in on July 30th. I'm likely moving away from Last.fm integration. It's such a ghost town anymore, reminiscent of a dusty player piano in a forgotten Old West saloon.

While I was very close to making my final move to GitHub, I never could get DataTables to work, which is weird, since I have no problems in doing so with a basic HTML file. After doing ALL sorts of Googling over the matter, I felt like outside of a random Reddit unresolved question from 3 years ago, I was the only person in the world to experience this.

So, I went back to the basics, and ran a brand-new instance of Jekyll. No problem. I did the same for the theme I'm using...bingo. Yeah, the inaptly-named minimal-mistakes has a glaring one! Now, I could spend time running down the exact issue, but as it is, I'm not exactly big on the author's breaking of front matter conventions, but C'MON, leaving DataTables off the table in a static page context?

What irks me is that I FINALLY had my design in place, very nearly replicating my WordPress install sans the dynamic elements, though I could very go with a JavaScript replacement for the countdown clock since computer clocks are far more accurate than they were back in the 90s.

I look forward to leaving all of this setup behind so that I can get back to thinking how I can optimize fitness.