Just to add to my list of app ideas I'll likely never get around to (notable entries include an app with an algorithm for translating light frequency to audio frequency in such a way that one could listen to images, an app for generating sheet music from bird song, and an app where you trace out as many "faces" as you can find for a given high def nature photo) … how 'bout an app where you start with a given image and, being constrained to the existing collection of pixel values (but not their initial locations) see what you can create out of them by moving them about.
.@manton Does Micro.blog's Micropub API support setting categorie(s) in the message headers? Seems to be the last thing to figure out before creating myself a fresh posting shortcut.
Update: nevermind, found the Micropub standard, assuming Micro.blog's implementation conforms.
Yet another update: It does.
The f$&k-around-with list for the bookshelves plugin.
plugin-gallery (a README Experience)
A plugin for Micro.blog that is effectively a glorified wrapper for an invocation of plugin-lightbox's
gallery
partial, introduced by optional title and description elements and promoted to its own standalone page. The code for this plugin lives hereplugin-banner (a README Experience)
A Micro.blog plugin for dropping page-specific banners into your theme. Its code lives here
Okay … whatever. So I guess the Micro.blog READMEs have their own page now.
plugin-plausible (a README Experience)
A plugin for Micro.blog for adding Plausible Analytics. Its code lives here.
When you waste 45 minutes, give or take, because you have to debug the GD static site generator in order to get it to generate a page highlighting its own code using its own highlighter (turns out, the
highlight
shortcode ≢ code fence parsing … stellar work fellas).What f$&king YAML? Hugo, you're such a d$ck.
plugin-social-media-links (a README Experience)
A Micro.blog plugin for injecting your social media account links into the page
<head>
with a partial suitable for profile display. It's code lives here.plugin-table-of-contents (a README Experience)
A plugin for Micro.blog for generating a slide-over table of contents. Its code lives here.
plugin-conversation (a README Experience)
A plugin for Micro.blog with a partial for including replies and webmentions for post pages. The plugin also supports blacklisting individual responses to prevent their appearance. Its code lives here
plugin-programmable-search-engine (a README Experience)
A plugin for Micro.blog for adding a site search interface using Google’s programmable search engine API. It’s code lives here
Been awhile since I've wonder whether I oughta just serve my site from the office desktop and hand-roll an app for pushing content over to feed the site (as well as the custom cross-post routines I could tailor to fit my needs) … coded in Swift, head-to-toe.
I may as well move all the plugins back inside my theme so I can bundle resources and optimize page loads.
Show me a cooler lightbox shortcode after test driving the section one examples with the adorable shots of Murphy and I'll owe you a beer.
plugin-lightbox (a README Experience)
A plugin for Micro.blog for presenting a slide carousel containing images and/or videos. Its code lives here.
Okay, Micro.blog plugin consumers … y'all think my plugins should default to having fingerprint on or off? The only reason to default to having it off would be convern over cache-busting (I would assume only full rebuilds or plugin modifications cause the link to change). @sod
plugin-category-cloud (a README Experience)
A plugin for Micro.blog that creates a page displaying links to your categories layed out as a category cloud. Its code lives here.
plugin-cards (a README Experience)
plugin-cards is a Micro.blog plugin for generating link preview cards on various platforms (including your blog) as well as generating structured data for search engine consumption. Its code lives here.
The rough draft up on the test blog of the walkthrough (that has turned into the updated README) for plugin-cards. Probably dot the 'I's and cross the 'T's tomorrow.
When you waste an hour before you realize you were using
:=
where you meant to use=
(because having two separate assignment operators is poor language construction).Sooo … since I figured out how to create my own Chroma style to use with Hugo 0.91's automagical syntax highlighting for fenced (and labeled) code, I've totally dropped plugin-prism. Other than my moondeer theme, the only other survivor is the shortcode for tricking Hugo into rendering its own code as example code rather than attempting to invoke it.
I figured I may as well generalize what was a shortcode for embedding shortcodes so that it would embed whatever TF I happened to want it to. So I did, calling this new rendition
preserve
.The example output below tricks Hugo into not tagging the
+++
lines that fence the front matter for a Markdown Hugo content file with the.err
class and into actual printing the shortcode in the content block below the front matter.+++ title = "Bookshelf" description = "Book collections" type = "bookshelf" +++ {{< plugin-bookshelves >}}
To get this example to render in this little post looks something like:
{{< preserve "+++" >}} title = "Bookshelf" description = "Book collections" type = "bookshelf" {{< preserve "+++" >}} {{< preserve "{{< plugin-bookshelves >}}" >}}
So what complex logic must one stick into the code for
layouts/shortcodes/preserve.html
to get this all to work? All you need is this :{{ .Get 0 }}
Side note: more trickery may actually be necessary for this shortcode to work outside of a code fence. Totally didn't work when I tried to render that list bit as inline code.
plugin-bookshelves (a README Experience)
A plugin for Micro.blog that creates a page displaying multiple bookshelves. Its code lives here.
Bet I just located the issue. I had an HTML comment between blocks in
layouts/post/single.html
leftover from when I was double checking the microformat. Those little f$&kers are notorious for silently causing all kinds of issues.