.@manton here's some strange I'll try to get to the bottom of tomorrow.

With the previous theme reinstalled, everything builds … and the harmless errors are spawned by my conversations plugin.

With the latest theme version installed, the errors are no longer logged…

and it looks like everything builds (tags from homepage head)…

but … if you check the head tags for a post page…

the previous theme version's pages are there. It will be interesting to see if this new post will be permalinked … because it seems like what most likely happened was that everything looked right until I triggered the full rebuild for the first time with v180 installed.

The state of the plugins before I go about updating READMEs (thereby discovering whether everything is actually working):

.@manton Still curious about these push failures. Do these indicate a single failed push to some device or a full on failure? Did you and @maique receive the mentions from the the posts that failed to push?

.@manton If I end up selling you on the data templates for parameters … we could add an entry to plugin.json for registering the config files for display in the installed plugins list … perhaps even having them open in their own editor from there to make it less frightening.

.@manton after sifting through posts and ripping out my unnecessary shortcode invocations, I can't seem to clear these out of the log. Some builds are clean, others are not. Could this be a per server cache issue where the servers I hit with full rebuild clear the cache?

.@manton How did the Micro.blog @ulyssesapp integration come about? The sooner they learn that they oughta export the exact same labeled code fence when publishing as they do when exporting Markdown the better (seeing as that's all you need to trigger syntax highlighting).

Updated READMEs just around the corner.

The lightbox plugin now allows for per gallery invocation grid width and row height configuration thanks to the CSS grid module (y'all webdevs have it soooo f$&kin' easy these days).

The home-rolled audio preview cards de-borked:

.@manton @pratik your custom theme is your custom theme. It exists entirely separately from the plugin. The way that Hugo merges directories means that my plugin can look for a particular data file that exists entirely outside of the plugin. This is why I use a different path (dash-cased) to avoid collisions.

I take the data file templates / default parameter value files held by the plugin … copy/paste into a single file … add adjust for file level (add [Config], [Style], and convert to [Bookshelves.Registered]) … and then save that in my single custom them (Moondeer).

You can see all my plugin configurations living in my custom theme:

Y'all are making it more complicated than it actually is.

Suppose I should de-bork my home-rolled audio preview cards.

Rabbit hole Exhibit A:

Category posts are assigned images for preview cards ∴ posts without any images oughta default to a their category's image rather than a site default image.

Posts can belong to more than one category ∴ it would be cool-as-f$&k if all a post's categories were represented in the preview card image.

Ooh … ooh … I bet I could stick the category images under the assets directory and, using the Hugo pipe image manipulation API, generate these hybrid preview card images on the f$&kin' fly…

Thinking of adding support for book comments to plugin-bookshelves when in list view so I can create a shelf for the books that shaped me coming up and in college … and that I still mention from time to time (like yesterday).

.@manton Blog selection here consistent with the rest of the interface, while not a big deal, would save the following trip when you want to rebuild a blog that isn't the blog in focus: Design → Select Blog → Account → View Logs → Rebuild Selected Blog

Side note: @JohnPhilpin @pimoore

If y'all are talking conversations, I can help … having recently refactored my conversations plugin.

You can check out an example post with webmentions bounced over from Twitter by Brid.gy here

Or see how @sod made the cards wicked cool here

Or see @manton and I talk plugin version resolution here

All my visible HTML is element producing plugins are built to be callable from custom themes (like my own). I check for the partial and call it when it exists. You can do the same check (how I imagined this stuff would eventually work) … or cannibalize anything you see that you like. Whatevs.

Update: of course, the README is out of date … the data directory plus the sass file tells the story.

Okay … I was off by four … their are 16 plugins.

If you're reading this off the MB timeline … and you're interested in any of the dozen or so plugins gonna drop after updated READMEs … and you're afraid to select Hugo v0.91, holler, I'll help you transition. I'm ready to bury v0.54.

And then there were two…

(plus all their f$&king READMEs (눈_눈))

The current state of the refactor list. They all require Hugo 0.91 (if you need help updating your rig from 0.45 just holler). None of the READMEs have been updated #ADHD.

.@manton version logic is off.

side note: I almost have the bookshelf plugin refactored. Just touching up the styling and I will need to update the README for my new parameter paradigm.

.@manton it would be great to have a toggle that allowed us to switch the inclusion of the --minify flag on and off for the Hugo build of our sites. I am borderline OCD about whitespace in the generated HTML (which is a pain in the ass to format consistently).

'Bout to find out if I just wasted six hours or so because I managed to f$&king forget that using HTML comment syntax (containing zero Hugo code) inside of Hugo templates leads to silent f$&king failures where page generation is concerned.

Updated plugin-conversation (aside from the README) to utilize Sass style parameters and statically fetched JSON feeds. These two comments happen to be reply tweets bounced over by Brid.gy:

.@manton Also be helpful to do something about this (I can't even discern anything noticeable this time).

The current state of the plugin refactoring list:

Okay … whatever … I removed the need for the query parameter and added support for cross posting external preview cards in plugin-cards by embedding the card in an a comment and using Javascript to exchange the element content.