Check out my new TESTING page where I hope to continue testing new features. Also, be sure to have a look at my new HIKES site and especially some of the “highlighted” hikes that are listed in bold there.
Note that HIKES used to be a “section” here, but there are a lot of them so I made a site just for them.
Mackenzie, my daughter, and I created this post documenting my wife’s Finale workflow for scanning and editing music on her Mac. We did this for my wife to celebrate her birthday preserve her sanity. Well, it was worth a shot. The birthday idea seemed more romantic, but mental health comes first.
The document was created using a process we recently built and documented in Creating Better Documentation. In this instance of the process we tried to annotate in yellow screen capture elements that need attention, and used red annotation to indicate things that require input or action of some kind. In some of the later images we failed and things that should be red were left highlighted in yellow. Sorry.
In case it’s needed later, I captured all of the sites listed above in a OneTab page.
Gating My Content & More
I started to create a lengthy post here but ended up moving it to my professional blog. So, please look for the start of this subject in Gating My Content & More - Parts 1 and 2.
😦
Last evening I took a shot at implementing the Netlify Identity tricks from the aforementioned article, but could not easily get it to work. The problem, I think, is that the https://Wieting.TamaToledo.com on Netlify already uses Netlify Identity for authentication of my Netlify CMS forms, and adding a second, separate instance of that service isn’t trivial and perhaps isn’t even feasible. I also tried implementing some quick Staticrypt CLI protection but that also failed. Netlify does provide a really quick and painless solution, but it costs $20/month, at a minimum, to enable it.
Pay close attention to the subtitle above! A couple of days ago I was working on content for Tama-Toledo Community Visioning and I added a large socialmedia.zip file to the source repo, and then very stupidly pushed it to GitHub and the repo’s main branch. Naturally, the push didn’t finish so I removed the file and pushed a new commit to “remove it permanently”. Well, that ain’t how git works!
Today I discovered a slick trick for “local” development of my first Hugo Module. The guidance I used was found in Working with Hugo Module Locally and it was spot-on! In my case the key was the additon of one line, two if you include the comment, to my project’s config.yml file:
// Innocent line below!
replace github.com/SummittDweller/hugo-timeline => /Users/mark/GitHub/hugo-timeline
What follows is an excerpt from this blog’s README.md file.
I’ve successfully added the code to drive a new /timeline page as part of this blog, but I did so “locally”, and now I’d like to repeat the process but using the aforementioned SummittDweller/hugo-timelinemodule.
Ya’ gotta love Hugo! I just completed my first Jekyll-to-Hugo conversion, and made it a Hugo module. It’s taken me a couple of years to realize the power of Hugo modules, and I have to say it’s AWESOME, and perfectly implemented.