It’s long overdue but this evening I managed to re-spin my the-Helge-Project genealogy website by adding NPM and Pagefind. Update: The result IS now available at https://tree.mcfate.family or the old site at https://helge.mcfate.family.

It should behave just like before with one BIG exception… the SEARCH bar near the top of the page.

Last night I was doing some arm-chair research for my grandmother’s 1926 travel journal and started wondering who the family would find when moving to Long Beach, CA. I quickly lamented that my https://helge.mcfate.family site had no “search” feature of any kind… How was I going to find that Long Beach connection?

Well, now that’s a piece of cake. Try it for yourself…

https://tree.mcfate.family

Mackenzie’s appointment was quick and all good news so we managed to get away for lunch.

The stupidity has already begun. There are just a couple EV charging stations here in the ramps, specifically in ramp three, but that ramp is marked as “full” even though I can see two open plug-in spaces. Am I allowed to go park there? No, because the ramp is “full”. The University of Iowa traffic “control” never fails to disappoint, they consistently STUPID.

My mother-in-law needed a little assistance, getting her electric snowblower going. Mission accomplished, now back to work.

This evening I created the 1926 McFate Travel Journal repo from the grinnell-college-CB-base template repo. Now I need a script that will break the primary .md document into smaller chunks, and update them in Azure Blob storage.

So I made the decision last night to implement an instance of CollectionBuilder to document my grandmother Miriam’s 1926 travel journal. I posted this from roughly where that journey began, my grandparent’s old farm in northern Poweshiek County.

This is really just another test of my system as we’re waiting on friends to go walking around the lake that isn’t anymore.

Creating this new post from my phone this morning while I visit the farm.

This test should return an accurate timestamp PLUS a valid “location” and “coordinates” from Drafts.

Thinking ahead, the “Publish Micropost to My Blog” script needs a couple more things:

• The “title:” field should automatically populate from the Draft title (first line) and it should be in TitleCase.
• Coordinates in Toledo or Tama (or other frequent stops) should get location tags without having to call the PositionStack API.

I modified the # solovyov.net blog post publish script giving it a new name of Publish Micropost to My Blog and so far it’s working nicely! It does not insert the location: or coordinates: values as I’d like yet, but stay tuned!