Example number 8-zillion-and-1 why Hugo is a pain in my a$$.

$Params := (.Scratch.Get "plugin-cards").Params.TwitterOG … f$&kin' nil

$Params := (.Scratch.Get "plugin-cards").Params
$Params = $Params.TwitterOG … the map I f$&kin' loaded

Thanks for the three-hour tour figuring that sh$t out Hugo.

Okay @manton … explain what I'm looking at. The test blog rebuilds fine. I made the mistake of trying to temporarily mess around with my main blog to try and capture some data for a plugin walkthrough. Now it doesn't want to rebuild. I see a whole lot of +3 minute penalties. Is it possible the timer isn't firing or is something else going on?

Got halfway through that walkthrough @JohnPhilpin and then I started refactoring sh$t … coming down the homestretch though, I believe *knock-on-wood*.

Side note: here's me using my own site search plugin to double check the spelling of your last name.

So plugin-cards (version 4.0.7) is kinda epic. Gonna work up a walkthrough today for me fellow Micro.bloggers.

Well that didn't take long. Just set yourself up with an h1 tag with a data-card-title attribute and style that f$&ker to be removed.

The irony is now I need to figure out a way to control the title behind the scenes, as actually providing a title gimps the video viewing in the Micro.blog timeline and themes set to summarize titled posts.

Proof positive with regard to that previous, previous post.

Well, would you look at that? Twitter player cards are now a thing in the cards plugin. Just slap a ?card-video query to the end of your video link. Can't believe I didn't think of this earlier @manton.

Side note: you'll want to title your post and slap in something to pick up as the description until I decide how to register those values invisibly.

So I guess we can access the plugin.json file @manton, but its contents will be that of the file from the plugin that wins the merge battle.

F$&k it, went ahead and fussed with the cards plugin again. Say hello to horizontal cards.

Created a partial for walking the structure of my Micro.blog Hugo build. Not sure why I did it. Also no sure why the recursion is hit or miss.

Thinking of creating a Micro.blog plugin for tracking and navigating series (primarily to make sense of my programming category).

A plugin for Micro.blog for adding a site search interface using Google’s programmable search engiine API. It’s code lives here

Read More

While I finish up the README for plugin-programmable-search-engine, thought I’d go ahead and toss out the list of plugin parameters … see if I could give @JohnPhilpin a bit of a fright.

Read More

.@JohnPhilpin

Since you'd only have seen the video if you were using Gluon, here, again, is a demonstration of how to load non-sponsored plugins via GitHub repository URL:

The programmable search engine Micro.blog plugin is done but for the README explain how to use it.

When you've blown through your daily 10,000 query limit set by Google when using their programmable search engine custom search API right on the brink of finalizing the parameterization of CSS variable values for your Micro.blog plugin (and finally being done with it):

Animating via CSS transition and the manipulation of custom CSS variables (which will, of course, end up as plugin parameters) from Javascript. Bootstrap class name congestion can go ahead and f$&k off now.

So I'll definitely come back to touch up the bookshelf plugin after I'm done piddling with this site search plugin. It was the first plugin I did … so it's missing all the best-practices I've been codifying as well as all the tricks I've learned along the way.

.@JohnPhilpin @pimoore @maique @artkavanagh @odd @agilelisa @frostedecho @tda

I suppose another good primer for my plugins would be a walkthrough explaining all the ways I subvert @manton's web-client-interface-based Hugo configuration in order to grab control over more of the build process:

config directory allows for safe, opt-in overriding/supplementing of things like the main navigation menu, the site.Author values (which you can straight up make up your own if you remember to access them in all lowercase

data directory allows you to drop in files with configuration data that become more easily accessible than plugin parameter values and more safely accessed as Hugo automatically parses them appropriately where as the plugin parameter interface saves everything as a string value

That all sounds scary, but in the end, what it means is that all my (complex) plugins really ask of y'all is to fill out a config file like a form of parameter values … and by making them TOML files included in the plugin itself I get to set you up with a template where I can add comments exaining how each value is used.

The Micro.blog programmable search engine plugin is getting damn close to finished now.

Closing in on a custom site search Micro.blog plugin.

What would really make this sick, @manton, would be letting me drop a hint to your cross-post parser (perhaps via data attribute tag with a URL value) that when cross-posting the cardify-card div should be replaced with a simple link so that other platforms generate their own preview cards in its place.

Now that I've injected Bootstrap, rolling my own preview cards by Hugo shortcode is even easier.

A footer beneath a post with navigation to the next / previous posts in the current section and a <nav> list in the middle with links to the current post's categories that behaves responsively with regard to screen real estate in that when there are too many categories for an itty bitty screen the category links know to ditch their bullet divider and stack themselves vertically … yeah … I gots it.

iPhone Portrait:

iPhone Landscape:

A Pair of iPad Safari Windows:

// Next/Prev
nav#next-prev {
  display: grid;
  grid-template-columns: 100px auto 100px;
  grid-template-areas: "next categories prev";
  margin: 2em 0;
  // width: 350px;

  @include media-breakpoint-up(sm) { width: 100%; }
  
  span {
    align-self: center;
    
    &#next { grid-area: next; justify-self: start; }
    
    &#prev { grid-area: prev; justify-self: end; }
    
    a {
      @include eaves-font($np-link-weight, $np-link-style);
      color: $np-link-col;
      &:hover { color: $np-link-hov-col; }
    }
    
  } // span
  
  nav#category-list {
    grid-area: categories;
    max-width: 100%;
    [@include](https://micro.blog/include) hstack(wrap, 
                    $justify: center, 
                    $align: baseline, 
                    $gap: 0.25rem);
    place-self: center;
    line-height: $line-height-sm;
      
    .category-link {
      text-align: center;
      @include eaves-font($np-cat-link-weight, $np-cat-link-style);
      color: $np-cat-link-col;
      
      &:hover { color: $np-cat-link-hov-col; }
            
      &:not(:last-child)::after { content: " •"; }
      
      @include media-breakpoint-down(sm) {
        &:first-child:nth-last-child(n + 3),
        &:first-child:nth-last-child(n + 3) ~ * {
          width: 100%;
          &::after { content: ""; }
        }
        
      }
    
      @include media-breakpoint-up(sm) {
        width: auto;
        &:not(:last-child)::after { content: " •"; }
      }
      
    }
  
  } // nav#category-list
  
} // nav#next-prev