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.

Okay … whatever … I put the Javascript back into plugin-cards supporting the cardify query parameter and it only gets loaded when a page actually contains a link with the query parameter. The use case is cross posting preview cards.

Well … none of that sh$te worked. Still an either or scenario where the preview card is concerned … in the blog post … or everywhere else.

The irony of rolling my own preview cards statically … now I have to figure out how to keep the HTML in my post but send the cardified link when cross posting.

CC @sod @manton

README isn't up to date … but thanks to the tip from @sod … plugin-cards now generates preview cards for external links … and the whole thing is done statically via shortcode.

.@manton Side note: getting log entries like the one below, thought you might be interested.

.@manton Another option might be downloadable logs. These could then be opened with an application built for filtering log files (like Console on OS X).

.@manton Is it possible to get more of these error messages or are you receiving them truncated? The structure of my invocations causes these messages to truncate just when they are about to become helpful.

Here's a nice example of the kind of ridiculous I must embrace when writing Hugo code (f$&k I miss Swift). What you are looking at is a simple check for the use of a pair of shortcodes (hacked to f$&k so it works on the homepage, taxonomy pages, and single pages).

cc @sod

Thanks to @sod, totally refactored the cardify portion of plugin-cards (not pushed yet) … no more Javascript plus support for external links … 'course now I'll have to rework that monster walkthrough I've yet to finish. (눈_눈)

Probably time for Gluon to handle gifs and video, wouldn't you say? You'd think at some point I'd be able to leave the web client behind without writing the app myself that replaces its use.

Being that Hugo is server-side, were I able to fetch HTML the way I'm able to fetch JSON, I could create a plugin for generating preview cards for external links within posts. Why I'm fixated on thinking up things I could do is beyond me.

Gonna have to reread the Hugo documentation in its entirety to recall all the things I wanted to tinker with that I can now actually tinker with (since @manton kindly updated our Hugo API … making the documentation relevant again).

#Unbummed