Wolf Noble

https://oostens.me/posts/hugo-shortcodes-with-markdown-gotchas/ geekdoc has a good expand shortcode that can be used for this... but it comes with some interesting caveats. https://github.com/thegeeklab/hugo-geekdoc/discussions/707 https://github.com/wolfspyre/hugo-geekdoc/tree/expand

yeah.. there’s a few ways to make this less fucky™️ my intent with submitting this as-is was to come to the party with beer… IE this **works** and serves as...

I [reached out to tailwind here][twd12482][^1]. Will followup as that conversation unfolds. [twd12482]: (https://github.com/tailwindlabs/tailwindcss/discussions/12482) [^1]: (https://github.com/tailwindlabs/tailwindcss/discussions/12482)

definitely different, for sure... I was going with divination https://en.wikipedia.org/wiki/Divination https://en.wikipedia.org/wiki/Greek_divination To convey the voodoo/waving of hands/consumption of snake oil/ etc... Because we're creating a secondary truthy source, and blindly...

so whats next here?

I've since refined the way **I'm** presenting the [currently usable colors here](https://wolfspyrelabs.static.wolfspyre.io/hugo-kisso/wplshortcodes/snippits/wplshortcodes/colorgems/) I could add this into the PR if ya want, but I figured that the point was to...

oddly enough, I was looking into something similar: https://oostens.me/posts/hugo-inline-spoiler-shortcode/ aught work reasonably well? looks pretty straightforward: ``` {{/* https://oostens.me/posts/hugo-inline-spoiler-shortcode/ */}} {{- .Inner | safeHTML -}} {{/* CSS requirements: .inline-spoiler {...

@aajain-com Is there anything preventing this from being merged?

+1 I'd really like an easier path using hashicorp tools with a eucalyptus-backed cloud. What's preventing this from being integrated?

Is there anything that can be done to increase the likelihood of this getting merged?